Re: What's hapenned with pluto site?

Ok,

For a local project that uses maven 2 I was able to get it to use a 
locally built wagon by adding the following to pom.xml
   <build>
     <extensions>
       <extension>
         <groupId>org.apache.maven.wagon</groupId>
          <artifactId>wagon-ssh-external</artifactId>
          <version>1.0-beta-1-SNAPSHOT</version>
       </extension>
     </extensions>
   </build>

But I still couldn't affect remote directory permissions by setting 
<filePermissons/> or <directoryPermissions/>.

Elliot


Elliot Metsger wrote:
> Ug.  It is very difficult to get maven 2 to use a locally installed 
> wagon release, built from ASF svn trunk.  mvn site-deploy keeps on 
> pulling down the released version of wagon when I run site-deploy locally.
> 
> kill -9
> 
> Elliot
> 
> Elliot Metsger wrote:
>> David,
>>
>> I looked into the source code for Wagon - the transport thingy for 
>> Maven 2; I looked specifically in the wagon-ssh-external provider 
>> (http://svn.apache.org/viewvc/maven/wagon/trunk/wagon-providers/wagon-ssh-external/src/main/java/org/apache/maven/wagon/providers/sshext/ScpExternalWagon.java) 
>>
>> and it appears there may be a patch in for this issue.
>>
>> It's a little annoying; I can't easily tell from websvn if r392495 
>> made it into the most recent wagon release.  I think codehaus manages 
>> the issue tracker for wagon and with their server problems this week, 
>> their Jira isn't up.
>>
>> Bottom line is I'm not sure that the existing wagon ssh-external 
>> provider honors what you put in ~/.m2/settings.xml.  I've been unable 
>> to get the <directoryPermissions/> element to do anything meaningful 
>> on a work-related maven 2 site.
>>
>> Elliot
>>
>> Elliot Metsger wrote:
>>> Hi David,
>>>
>>> IIRC Pluto 1.1 is using Maven 2 right?
>>>
>>> I've not tried this but it may involve updating your <server/> in 
>>> ~/.m2/settings.xml: 
>>> http://maven.apache.org/maven-settings/settings.html#class_server
>>>
>>>     <server>
>>>       <username/>
>>>       <password/>
>>>       <privateKey/>
>>>       <passphrase/>
>>>       <filePermissions/>
>>>       <directoryPermissions/>
>>>       <configuration/>
>>>       <id/>
>>>     </server>
>>>
>>>   filePermissions     The permissions for files when they are created.
>>>   directoryPermissions     The permissions for directories when they 
>>> are created.
>>>
>>> I'm not sure what is supposed to go in the <filePermissions/> and 
>>> <directoryPermissions/> element.  An octal number?
>>>
>>> Elliot
>>>
>>> David H. DeWolf wrote:
>>>> Done.
>>>>  
>>>> I think you'll still have some issues with a couple.  It looks like 
>>>> Zheng's got some too.
>>>>  
>>>> Does anyone know how to make sure that when we do a maved 
>>>> site:deploy the appropriate permissions get set?
>>>>  
>>>> David
>>>>
>>>>     
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>     *From:* [email protected] [mailto:[email protected]]
>>>>     *Sent:* Thursday, May 25, 2006 3:33 PM
>>>>     *To:* [email protected]
>>>>     *Subject:* Re: What's hapenned with pluto site?
>>>>
>>>>
>>>>     Thank you Carsten,
>>>>
>>>>     I sent the email yesterday to your work address.
>>>>
>>>>     Specifically, the subdirectories still need write permission for
>>>>     group members, which David needs to do. All files should also have
>>>>     write permissions for group members. I'd rather not elaborate any
>>>>     further in this public forum for security reasons.
>>>>     /Craig
>>>>
>>>>
>>>>
>>>>     *Carsten Ziegeler <[email protected]>*
>>>>
>>>>     05/25/2006 02:27 PM
>>>>     Please respond to
>>>>     [email protected]
>>>>
>>>>
>>>>            To
>>>>         [email protected]
>>>>     cc
>>>>            Subject
>>>>         Re: What's hapenned with pluto site?
>>>>
>>>>
>>>>      
>>>>
>>>>
>>>>
>>>>     Craig Doremus schrieb:
>>>>      > I sent you (and Carsten) a note yesterday saying that I was
>>>>     trying to
>>>>      > deploy the site with the 1.1.0-beta1 documentation, but I 
>>>> there were
>>>>      > permission problems that probably led to the partial deployment.
>>>>     Can you
>>>>      > change the file and directory permissions to allow this?
>>>>      >
>>>>     Strange, I never got this mail - now I just rechecked and I 
>>>> think that I
>>>>     add a group write perm to all the files I added. There are still 
>>>> other
>>>>     files and dirs where this permissions is missing though.
>>>>
>>>>     Carsten
>>>>     --     Carsten Ziegeler - Open Source Group, S&N AG
>>>>     http://www.s-und-n.de
>>>>     http://www.osoco.org/weblogs/rael/
>>>>