ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tero Hagström (JIRA) <j...@apache.org>
Subject [jira] Commented: (IVY-764) ssh resolver sets very restrictive file permissions when publishing artifacts
Date Wed, 12 Mar 2008 09:56:46 GMT

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


Mime
View raw message