maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Moved: (WAGON-185) scpexe seems to deploy checksums with mode 700 instead of 644
Date Wed, 14 May 2008 07:37:28 GMT

     [ http://jira.codehaus.org/browse/WAGON-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter moved WAGONSSH-25 to WAGON-185:
--------------------------------------------

    Fix Version/s:     (was: 1.0-alpha-6)
                   1.0-alpha-6
      Component/s:     (was: wagon-ssh)
                   wagon-ssh
              Key: WAGON-185  (was: WAGONSSH-25)
          Project: Maven Wagon  (was: wagon-ssh)

> scpexe seems to deploy checksums with mode 700 instead of 644
> -------------------------------------------------------------
>
>                 Key: WAGON-185
>                 URL: http://jira.codehaus.org/browse/WAGON-185
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-ssh
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>            Priority: Blocker
>             Fix For: 1.0-alpha-6
>
>   Original Estimate: 15 minutes
>          Time Spent: 30 minutes
>  Remaining Estimate: 0 minutes
>
> this could be a configuration issue, or could be a wagon problem - unsure, so starting
at the place it is most obvious.
> It occurred under the previous deploy plugin too - so not a new issue.
> Here is the result:
> -bash-2.05b$ ls -alR
> .:
> total 24
> drwxr-xr-x    3 maven    maven        4096 Dec  5 00:31 .
> drwxr-xr-x   37 maven    maven        4096 Dec  5 00:28 ..
> drwxr-xr-x    2 maven    maven        4096 Dec  5 00:31 2.1-SNAPSHOT
> -rwxr-xr-x    1 maven    maven         331 Dec  5 00:31 maven-metadata.xml
> -rwx------    1 maven    maven          32 Dec  5 00:31 maven-metadata.xml.md5
> -rwx------    1 maven    maven          40 Dec  5 00:31 maven-metadata.xml.sha1
> ./2.1-SNAPSHOT:
> total 52
> drwxr-xr-x    2 maven    maven        4096 Dec  5 00:31 .
> drwxr-xr-x    3 maven    maven        4096 Dec  5 00:31 ..
> -rwxr-xr-x    1 maven    maven         339 Dec  5 00:30 maven-metadata.xml
> -rwx------    1 maven    maven          32 Dec  5 00:30 maven-metadata.xml.md5
> -rwx------    1 maven    maven          40 Dec  5 00:31 maven-metadata.xml.sha1
> -rwxr-xr-x    1 maven    maven        9083 Dec  5 00:28 maven-surefire-plugin-2.1-20051205.052752-1.jar
> -rwx------    1 maven    maven          32 Dec  5 00:28 maven-surefire-plugin-2.1-20051205.052752-1.jar.md5
> -rwx------    1 maven    maven          40 Dec  5 00:29 maven-surefire-plugin-2.1-20051205.052752-1.jar.sha1
> -rwxr-xr-x    1 maven    maven        1480 Dec  5 00:29 maven-surefire-plugin-2.1-20051205.052752-1.pom
> -rwx------    1 maven    maven          32 Dec  5 00:29 maven-surefire-plugin-2.1-20051205.052752-1.pom.md5
> -rwx------    1 maven    maven          40 Dec  5 00:29 maven-surefire-plugin-2.1-20051205.052752-1.pom.sha1
> The only reason this is a 2.0.1 blocker is because the deployment of m2 itself switched
from scp:// to scpexe://

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message