shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Les Hazlewood <>
Subject Re: [jira] Resolved: (SHIRO-156) SimpleAuthenticationInfo.merge does not merge principals if its internal principal collection is not mutable
Date Sat, 15 May 2010 07:13:49 GMT

It appears that there is a Confluence 'Site' page with a child of 'Banner':

I think this might be screwing things up, but I don't know for sure
what is going on.

I'm still genuinely curious why the files we published don't show up
though - maybe something having to do with mirroring?


On Sat, May 15, 2010 at 12:08 AM, Les Hazlewood <> wrote:
> Ok, the 'mvn site-deploy' command appeared to complete without any
> problem.  But now I'm thoroughly confused:
> I'm logged in to people@ and I'm in the following directory:
> [lhazlewood@minotaur:/www/]$ pwd
> /www/
> However, nothing comes up for this URL:
> Directory/file permissions look good.
> Any idea why we can't see it?
> On Fri, May 14, 2010 at 11:58 PM, Les Hazlewood <> wrote:
>> Ahah - thanks.  It has been a while since I've done a maven release (3
>> months?) and I used password-based authentication at the time.
>>> No, your own public/private SSH key pair, assuming you've created and
>>> authorized one. Technically you can use password authentication as
>>> well but then you'd need to put your password in the settings.xml. If
>>> you are not familiar with mvn deploy & wagon, see
>> Ah, OK.  I was reading this:
>> and noticed the 'gpg.passphrase' property (first preformatted block in
>> that page).  I set it to what I think is my passphrase and it is not
>> working - it keeps asking me to type in my password :/
>> But, I added my key to ~/.ssh/authorized_keys and all appears to be
>> working now - thanks for the help!
>>> And replying out-of-order to your follow-up question: the
>>> release-profile is the default profile activated by release plugin if
>>> useReleaseProfile is true (see
>>> The profile is
>>> there so we can deploy snapshot docs to constant location and release
>>> docs to location specified by the version, compare the associated urls
>>> in the respective distributionManagement sections.
>> Gotcha, thanks.
>> Les

View raw message