You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ben Hale (JIRA)" <ji...@codehaus.org> on 2007/11/20 14:58:57 UTC

[jira] Created: (MANTTASKS-100) Deploy tasks creates incorrect checksums

Deploy tasks creates incorrect checksums
----------------------------------------

                 Key: MANTTASKS-100
                 URL: http://jira.codehaus.org/browse/MANTTASKS-100
             Project: Maven 2.x Ant Tasks
          Issue Type: Bug
          Components: deploy task
    Affects Versions: 2.0.7
            Reporter: Ben Hale
            Priority: Critical


When releasing Spring 2.5.0, I used the maven deploy tasks to deploy all artifacts to a filesystem which were then uploaded for synchronization (http://fisheye1.cenqua.com/browse/springframework/spring/build-continuous.xml?r=1.18). 

However, now that users have started downloading them, it's come to our attention that the MD5 and SHA1 sums that the task created are incorrect (http://repo1.maven.org/maven2/org/springframework/spring-core/2.5/) for all artifacts.

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

[jira] Closed: (MANTTASKS-100) Deploy tasks creates incorrect checksums

Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MANTTASKS-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy closed MANTTASKS-100.
-----------------------------------

      Assignee: Herve Boutemy
    Resolution: Cannot Reproduce

I looked at the link to the repo you gave me.
I checked checksums for every files: {{spring-core-2.5-sources.jar}}, {{spring-core-2.5.jar}} and {{spring-core-2.5.pom}}
I found that they were correct for both .jar files, but incorrect for pom file.

I checked Maven Ant Tasks unit tests on my machine and found that the checksums were correct.

I checked the code: Maven Ant Tasks use deployment classes from maven-artifact-manager exactly like Maven itself.

Then I don't see where the tasks could have done anything different from Maven.

You say the artifacts were uploaded for synchronization: could the pom file have been modified during the transfert, like an end-of-line replacement with FTP?
I transformed the downloaded pom file with {{unix2dos}} command and calculated checksums: bingo, the new checksums are like those in checksum files.
Then the problem is in your transfert process.

> Deploy tasks creates incorrect checksums
> ----------------------------------------
>
>                 Key: MANTTASKS-100
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-100
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>          Components: deploy task
>    Affects Versions: 2.0.7
>            Reporter: Ben Hale
>            Assignee: Herve Boutemy
>            Priority: Critical
>
> When releasing Spring 2.5.0, I used the maven deploy tasks to deploy all artifacts to a filesystem which were then uploaded for synchronization (http://fisheye1.cenqua.com/browse/springframework/spring/build-continuous.xml?r=1.18). 
> However, now that users have started downloading them, it's come to our attention that the MD5 and SHA1 sums that the task created are incorrect (http://repo1.maven.org/maven2/org/springframework/spring-core/2.5/) for all artifacts.

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