This should have been fixed in wagon 1.0-alpha-6, which is included in
Maven 2.0.2.

What version are you using?

- Brett

On 1/25/06, Kathryn Huxtable <[EMAIL PROTECTED]> wrote:
> I have the same problem.
>
> Please, someone, tell us where to report this.
>
> -K
>
>
> On 1/24/06 10:50 PM, "Treloar, Barrie (SAPOL)"
> <[EMAIL PROTECTED]> wrote:
>
> > I am finding that when I deploy my snapshots to our internal repository that
> > the created files do not have group write permissions.
> >
> > My umask on that unix machine is 022, but from what I can tell I should not
> > have to change my umask because the <server> section of settings.xml can
> > specify both filePermissions and directoryPermissions.
> >
> > [EMAIL PROTECTED]:/usr/local/www/default/maven2_repositories > l
> > inhouse_snapshot/XXX/XXX/0.0.1-SNAPSHOT/
> > total 65
> > drwxrwsr-x    2 XXXXXXX  other        1024 Jan 25 15:17 ./
> > drwxrwsr-x    3 XXXXXXX  other         512 Jan 24 15:59 ../
> > -rw-r--r--    1 XXXXXXX  other         340 Jan 25 15:17 maven-metadata.xml
> > -rw-r--r--    1 XXXXXXX  other          32 Jan 25 15:17
> > maven-metadata.xml.md5
> > -rw-r--r--    1 XXXXXXX  other          40 Jan 25 15:17
> > maven-metadata.xml.sha1
> > ...
> > -rw-r--r--    1 XXXXXXX  other       10030 Jan 25 15:17
> > XXX-0.0.1-20060125.044219-5.pom
> > -rw-r--r--    1 XXXXXXX  other          32 Jan 25 15:17
> > XXX-0.0.1-20060125.044219-5.pom.md5
> > -rw-r--r--    1 XXXXXXX  other          40 Jan 25 15:17
> > XXX-0.0.1-20060125.044219-5.pom.sha1
> >
> > My settings.xml has the following entry:
> >         <server>
> >             <id>inhouse_snapshot</id>
> >             <username>XXX</username>
> >             <privateKey>XXX</privateKey>
> >             <filePermissions>664</filePermissions>
> >             <directoryPermissions>775</directoryPermissions>
> >         </server>
> >
> > My pom.xml has:
> >     <distributionManagement>
> >         <repository>
> >             <id>inhouse</id>
> >             <name>Internal Release Repository</name>
> >             <url>
> >
> > scp://XXX/usr/local/www/default/maven2_repositories/inhouse</url>
> >         </repository>
> >         <snapshotRepository>
> >             <id>inhouse_snapshot</id>
> >             <name>Internal Snapshot Repository</name>
> >             <url>
> >
> > scp://XXX/usr/local/www/default/maven2_repositories/inhouse_snapshot</url>
> >         </snapshotRepository>
> >         <site>
> >             <id>website</id>
> >             <url>scp://XXX/usr/local/www/default/projects/XXX</url>
> >         </site>
> >     </distributionManagement>
> >
> > There is one other email from the list on Nabble at
> > http://www.nabble.com/-M2-directorypermissions-ignored-during-deploy-t436786
> > .html#a1196148 that talks about directoryPermissions not working.  For them
> > filePermissions works fine.
> >
> > And a closed JIRA issue at http://jira.codehaus.org/browse/MNG-575 which
> > looks like issue raised to get filePermissions and directoryPermissions
> > added to settings.xml.
> >
> >
> > Is anyone able to point out what I have missed to get this to work?
> >
> > Cheers,
> > Barrie
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> --
> Kathryn Huxtable
> Middleware Architect
> Core Middleware
> Information Technology, a division of Information Services
> The University of Kansas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to