[
https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592023#action_12592023
]
hagis edited comment on IVY-764 at 4/24/08 5:31 AM:
------------------------------------------------------------
Not quite there yet, I still cannot publish artifacts so that they would be
readable by other users.
I would have expected the publishPermissions attribute to work the same way as
umask, but it seems to be the negative. Alone, this would be acceptable, if
properly documented, but if I set the publishPermissions attribute to a value
that produces the file permissions that I want, the publishing of the ivy
files, sha1 and md5 files fails!
Case 1:
Used value for publishPermissions: 0222
resulting file permissions:
{code}--w------- 1 th dev 1263 Apr 24 15:07 upon-20080424150713.jar{code}
expected permissions:
{code}-r--r--r--{code}
Case 2:
Used value for publishPermissions: 0022
resulting file permissions:
{code}---------- 1 th dev 1263 Apr 24 14:59 upon-20080424145932.jar{code}
Only jar file published, sha1, md5, and xml files not:
{code}/g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts
for com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException:
/tmp/ivytemp49772sha1 (Permission denied){code}
expected permissions:
{code}-rw-r--r--{code}
all files should have been published
Case 3:
Used value for publishPermissions: 0666
resulting file permissions:
{code} -rw-r--r-- 1 th dev 1263 Apr 24 15:16 upon-20080424151611.jar{code}
Only jar file published, sha1, md5, and xml files not:
{code}/g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts
for com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException:
/tmp/ivytemp17387sha1 (Permission denied){code}
expected permissions:
{code}----------{code}
all files should have been published
was (Author: hagis):
Not quite there yet, I still cannot publish artifacts so that they would be
readable by other users.
I would have expected the publishPermissions attribute to work the same way as
umask, but it seems to be the negative. Alone, this would be acceptable, if
properly documented, but if I set the publishPermissions attribute to a value
that produces the file permissions that I want, the publishing of the ivy
files, sha1 and md5 files fails!
Case 1:
Used value for publishPermissions: 0222
resulting file permissions:
--w------- 1 th dev 1263 Apr 24 15:07 upon-20080424150713.jar
expected permissions:
-r--r--r--
Case 2:
Used value for publishPermissions: 0022
resulting file permissions:
---------- 1 th dev 1263 Apr 24 14:59 upon-20080424145932.jar
Only jar file published, sha1, md5, and xml files not:
/g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts for
com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException:
/tmp/ivytemp49772sha1 (Permission denied)
expected permissions:
-rw-r--r--
all files should have been published
Case 3:
Used value for publishPermissions: 0666
resulting file permissions:
-rw-r--r-- 1 th dev 1263 Apr 24 15:16 upon-20080424151611.jar
Only jar file published, sha1, md5, and xml files not:
/g/projects/ivytest/upon/build.xml:112: impossible to publish artifacts for
com.profium.ivytest#upon;[EMAIL PROTECTED]: java.io.FileNotFoundException:
/tmp/ivytemp17387sha1 (Permission denied)
expected permissions:
----------
all files should have been published
> make it possible to specify permissions of published files for the SSH
> resolver
> -------------------------------------------------------------------------------
>
> Key: IVY-764
> URL: https://issues.apache.org/jira/browse/IVY-764
> Project: Ivy
> Issue Type: Improvement
> Affects Versions: 2.0.0-beta-2
> Reporter: Tero Hagström
> Assignee: Maarten Coene
> Fix For: 2.0-RC1
>
>
> When we use the ssh resolver to publish artifacts to a repository on our
> server, the access permissions of the created files only allow reading by the
> user that published the artifacts. As a result, no one else can get the
> artifacts from the repository, which completely defeats it's purpose.
> File permissions look like this:
> -rw------- 1 atu dev 875 Mar 10 12:34 core-20080310123411.jar
> -rw------- 1 atu dev 40 Mar 10 12:34 core-20080310123411.jar.sha1
> -rw------- 1 atu dev 32 Mar 10 12:34 core-20080310123411.jar.md5
> -rw------- 1 atu dev 166 Mar 10 12:34 ivy-20080310123411.xml
> -rw------- 1 atu dev 40 Mar 10 12:34 ivy-20080310123411.xml.sha1
> -rw------- 1 atu dev 32 Mar 10 12:34 ivy-20080310123411.xml.md5
> I could not find any way to configure or otherwise affect the file
> permissions. Is there a way?
> BTW, with Ivy 1.4.1 the permissions looked like this:
> -rw-rw-r-- 1 th dev 877 Mar 6 10:08 core-20080306100813.jar
> -rw-rw-r-- 1 th dev 40 Mar 6 10:08 core-20080306100813.jar.sha1
> -rw-rw-r-- 1 th dev 32 Mar 6 10:08 core-20080306100813.jar.md5
> -rw-rw-r-- 1 th dev 166 Mar 6 10:08 ivy-20080306100813.xml
> -rw-rw-r-- 1 th dev 40 Mar 6 10:08 ivy-20080306100813.xml.sha1
> -rw-rw-r-- 1 th dev 32 Mar 6 10:08 ivy-20080306100813.xml.md5
> We will now fall back to using Ivy version 1.4.1, for the time being.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
