Ah. The sticky bit is the part I missed. I had set the directory perms to
775 and the file perms to 664 in the settings.xml.

The files got the perms and the g:w didn't take on the directory.

-K


On 1/26/06 12:21 PM, "Orjan Austvold" <[EMAIL PROTECTED]> wrote:

> Hi again,
> 
> I forgot to mention that the reason is that most (new) ssh server
> implementations do not allow for umask changes on scp/sftp.
> 
> --
> Ørjan
> 
> Orjan Austvold wrote:
>> Hi,
>> 
>> Add a <filePermissions> element in the server element in settings.xml.
>> Mine is
>> 
>> <filePermissions>664</filePermissions>
>> 
>> We also had to set the sticky group bit on the repository directory to
>> allow for users to overwrite metadata files on which other users
>> previously had released.
>> 
>> -- 
>> Ørjan
>> 
>> 
>> Kathryn Huxtable wrote:
>> 
>>> I'm using 1.0-alpha-6.
>>> 
>>> Ummm... Did I mention that I'm using scpexe in order to not put a
>>> password
>>> or passphrase in a file?
>>> 
>>> If I use sftp it works.
>>> 
>>> -K
>>> 
>>> 
>>> On 1/26/06 12:04 AM, "Brett Porter" <[EMAIL PROTECTED]> wrote:
>>> 
>>> 
>>>> 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-t436
>>>>>> 786 
>>>>>> 
>>>>>> .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]
>>>> 
>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> 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]
>> 
> 
> 
> ---------------------------------------------------------------------
> 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