[
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.
