You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Tero Hagström (JIRA)" <ji...@apache.org> on 2008/03/10 12:43:48 UTC
[jira] Created: (IVY-764) ssh resolver sets very restrictive file
permissions when publishing artifacts
ssh resolver sets very restrictive file permissions when publishing artifacts
-----------------------------------------------------------------------------
Key: IVY-764
URL: https://issues.apache.org/jira/browse/IVY-764
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Reporter: Tero Hagström
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.
[jira] Commented: (IVY-764) ssh resolver sets very restrictive file
permissions when publishing artifacts
Posted by "Tero Hagström (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577778#action_12577778 ]
Tero Hagström commented on IVY-764:
-----------------------------------
We added a cron job on the server that chmods all files in our repository, so we currently have a clumsy workaround.
How is the Ivy ssh resolver supposed to work with regard to the file permissions set for the published files?
> ssh resolver sets very restrictive file permissions when publishing artifacts
> -----------------------------------------------------------------------------
>
> Key: IVY-764
> URL: https://issues.apache.org/jira/browse/IVY-764
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Tero Hagström
>
> 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.
[jira] Commented: (IVY-764) ssh resolver sets very restrictive file
permissions when publishing artifacts
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576956#action_12576956 ]
Gilles Scokart commented on IVY-764:
------------------------------------
What is your umask? Did you set some special access right on the directory where you publish? Did it worked differently with ivy 1.4.1?
> ssh resolver sets very restrictive file permissions when publishing artifacts
> -----------------------------------------------------------------------------
>
> Key: IVY-764
> URL: https://issues.apache.org/jira/browse/IVY-764
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Tero Hagström
>
> 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.
[jira] Reopened: (IVY-764) make it possible to specify permissions
of published files for the SSH resolver
Posted by "Tero Hagström (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tero Hagström reopened IVY-764:
-------------------------------
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;working@th-laptop: 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;working@th-laptop: 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.
[jira] Commented: (IVY-764) make it possible to specify permissions
of published files for the SSH resolver
Posted by "Tero Hagström (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587502#action_12587502 ]
Tero Hagström commented on IVY-764:
-----------------------------------
Thanks, folks!
We'll give it a try as soon as we can, hopefully next week.
> 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.
[jira] Resolved: (IVY-764) make it possible to specify permissions
of published files for the SSH resolver
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene resolved IVY-764.
-------------------------------
Resolution: Fixed
I think I've fixed it in trunk.
It's now possible to specify the permissions of the published files with the "publishMode" attribute on your ssh resolver. If this attribute is not specified, it defaults to "0600".
Could you please test this and provide us some feedback? I don't have such a repository to test it myself.
> 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.
[jira] Commented: (IVY-764) make it possible to specify permissions
of published files for the SSH resolver
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586961#action_12586961 ]
Maarten Coene commented on IVY-764:
-----------------------------------
As discussed on the ant-dev mailinglist, the attribute has been renamed to publishPermissions.
> 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.
[jira] Commented: (IVY-764) make it possible to specify permissions
of published files for the SSH resolver
Posted by "Tero Hagström (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597871#action_12597871 ]
Tero Hagström commented on IVY-764:
-----------------------------------
Still working.
> 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.
[jira] Assigned: (IVY-764) ssh resolver sets very restrictive file
permissions when publishing artifacts
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene reassigned IVY-764:
---------------------------------
Assignee: Maarten Coene
> ssh resolver sets very restrictive file permissions when publishing artifacts
> -----------------------------------------------------------------------------
>
> Key: IVY-764
> URL: https://issues.apache.org/jira/browse/IVY-764
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Tero Hagström
> Assignee: Maarten Coene
>
> 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.
[jira] Commented: (IVY-764) ssh resolver sets very restrictive file
permissions when publishing artifacts
Posted by "Tero Hagström (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584468#action_12584468 ]
Tero Hagström commented on IVY-764:
-----------------------------------
Ping?
How is the Ivy ssh resolver supposed to work with regard to the file permissions set for the published files?
> ssh resolver sets very restrictive file permissions when publishing artifacts
> -----------------------------------------------------------------------------
>
> Key: IVY-764
> URL: https://issues.apache.org/jira/browse/IVY-764
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Tero Hagström
>
> 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.
[jira] Updated: (IVY-764) make it possible to specify permissions
of published files for the SSH resolver
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene updated IVY-764:
------------------------------
Fix Version/s: 2.0-RC1
Issue Type: Improvement (was: Bug)
Summary: make it possible to specify permissions of published files for the SSH resolver (was: ssh resolver sets very restrictive file permissions when publishing artifacts)
> 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.
[jira] Commented: (IVY-764) make it possible to specify permissions
of published files for the SSH resolver
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597610#action_12597610 ]
Maarten Coene commented on IVY-764:
-----------------------------------
great!
I've just made another change to improve backwards compatibility with previous Ivy releases when the publishPermissions attribute has not been specified. Could you do another test with latest version to make sure it is still working for you?
thanks,
Maarten
> 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.
[jira] Resolved: (IVY-764) make it possible to specify permissions
of published files for the SSH resolver
Posted by "Tero Hagström (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tero Hagström resolved IVY-764.
-------------------------------
Resolution: Fixed
It works now, thanks!
The publishPermissions attribute works like 'chmod', not like 'umask', as I was previously assuming. That's just fine by me.
This is what I now get with publishPermissions="0644"
{noformat}
-rw-r--r-- 1 th dev 1845 May 15 08:57 upon-20080515085723.jar
-rw-r--r-- 1 th dev 40 May 15 08:57 upon-20080515085723.jar.sha1
-rw-r--r-- 1 th dev 32 May 15 08:57 upon-20080515085723.jar.md5
-rw-r--r-- 1 th dev 377 May 15 08:57 ivy-20080515085723.xml
-rw-r--r-- 1 th dev 40 May 15 08:57 ivy-20080515085723.xml.sha1
-rw-r--r-- 1 th dev 32 May 15 08:57 ivy-20080515085723.xml.md5
{noformat}
There is no permission denied problem now, it only appeared with the previous Ivy version with some values of publishPermissions.
> 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.
[jira] Commented: (IVY-764) ssh resolver sets very restrictive file
permissions when publishing artifacts
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584474#action_12584474 ]
Maarten Coene commented on IVY-764:
-----------------------------------
I would think the file permissions are defined by the umask. In your example, you use a different user for ivy-2.0 and ivy-1.4.1. Do they have the same umask?
> ssh resolver sets very restrictive file permissions when publishing artifacts
> -----------------------------------------------------------------------------
>
> Key: IVY-764
> URL: https://issues.apache.org/jira/browse/IVY-764
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Tero Hagström
>
> 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.
[jira] Commented: (IVY-764) make it possible to specify permissions
of published files for the SSH resolver
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596969#action_12596969 ]
Maarten Coene commented on IVY-764:
-----------------------------------
I was able to reproduce your problem with the file permissions. I've updated SVN trunk and I hope I've fixed it (at least it was working for me now). Could you please try again and post your result here?
Regarding the "Permission denied" error you get for the sha1, md5 and xml files: I've never had this error, so my guess is this is another problem. Do you have access to your /tmp dir?
> 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.
[jira] Issue Comment Edited: (IVY-764) make it possible to specify
permissions of published files for the SSH resolver
Posted by "Tero Hagström (JIRA)" <ji...@apache.org>.
[ 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;working@th-laptop: 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;working@th-laptop: 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;working@th-laptop: 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;working@th-laptop: 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.
[jira] Commented: (IVY-764) ssh resolver sets very restrictive file
permissions when publishing artifacts
Posted by "Tero Hagström (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577336#action_12577336 ]
Tero Hagström commented on IVY-764:
-----------------------------------
Umask on both local and server is 0022.
I was playing around with Ivy 1.4.1 earlier, and managed to publish files on the server so that their permissions were
rw-rw-r-, which is what I want.
I cannot reproduce that behaviour with ivy 1.4.1 anymore though. Now I get permissions rw------ with 1.4.1 too.
What affects the file permissions set for the published files?
> ssh resolver sets very restrictive file permissions when publishing artifacts
> -----------------------------------------------------------------------------
>
> Key: IVY-764
> URL: https://issues.apache.org/jira/browse/IVY-764
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Tero Hagström
>
> 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.