You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Thorsten Scherler (JIRA)" <ji...@codehaus.org> on 2010/01/18 13:43:55 UTC
[jira] Created: (MRM-1312) mda5 and sha are not generated for
snapshot jars
mda5 and sha are not generated for snapshot jars
------------------------------------------------
Key: MRM-1312
URL: http://jira.codehaus.org/browse/MRM-1312
Project: Archiva
Issue Type: Bug
Affects Versions: 1.2.2
Reporter: Thorsten Scherler
I found a way to reproduce our problems that we have with uploading
SNAPSHOT versions via the web-interface.
We tried with the following files
cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
For the version we put in the web form 1.0.0-SNAPSHOT.
The result is that archiva creates the mda5 and sha for the pom but not
for the jar.
As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
fine.
It seems that the version *-SNAPSHOT is not working. What is the best
approach to debug to find out what is going on and why archiva is not
creating the mda5 and sha file.
It sounds that the following threas may be releated to this issue:
http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
The problem seems to be in the create-missing-checksums consumer. The
> consumer is looking for a jar with a -SNAPSHOT in the filename but the
> actual file has a unique (timestamp + build number) snapshot version so a
> "no such file or directory" error occurs. It works if the version is
> -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> at the end) and therefore the version wasn't converted to a unique version
> format.
>
--
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] Updated: (MRM-1312) mda5 and sha are not generated for
snapshot jars
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1312:
----------------------------------
Fix Version/s: 1.3.1
> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
> Key: MRM-1312
> URL: http://jira.codehaus.org/browse/MRM-1312
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Thorsten Scherler
> Fix For: 1.3.1
>
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface.
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar.
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> >
--
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: (MRM-1312) mda5 and sha are not generated for
snapshot jars
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching closed MRM-1312.
---------------------------------
Resolution: Fixed
Thanks for the patch Marica! Patch applied to 1.3.x branch [-r916197|http://svn.apache.org/viewvc?revision=916197&view=revision] and merged to trunk in [-r916217|http://svn.apache.org/viewvc?revision=916217&view=revision]. I updated the timestamp variable name to avoid conflict when I merged this to trunk.
> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
> Key: MRM-1312
> URL: http://jira.codehaus.org/browse/MRM-1312
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Thorsten Scherler
> Assignee: Maria Odea Ching
> Fix For: 1.3.1
>
> Attachments: MRM-1312.patch
>
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface.
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar.
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> >
--
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] Assigned: (MRM-1312) mda5 and sha are not generated for
snapshot jars
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching reassigned MRM-1312:
-------------------------------------
Assignee: Maria Odea Ching
> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
> Key: MRM-1312
> URL: http://jira.codehaus.org/browse/MRM-1312
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Thorsten Scherler
> Assignee: Maria Odea Ching
> Fix For: 1.3.1
>
> Attachments: MRM-1312.patch
>
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface.
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar.
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> >
--
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] Commented: (MRM-1312) mda5 and sha are not generated for
snapshot jars
Posted by "Thorsten Scherler (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209230#action_209230 ]
Thorsten Scherler commented on MRM-1312:
----------------------------------------
Hi Maria,
thank you very much for your patch. We did a quick check and it seems to close this issue. ATM we cannot make all test case that we planed but we will do this Monday. As soon we have the result I will update the ticket again. Thanks agin Maria.
> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
> Key: MRM-1312
> URL: http://jira.codehaus.org/browse/MRM-1312
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Thorsten Scherler
> Fix For: 1.3.1
>
> Attachments: MRM-1312.patch
>
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface.
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar.
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> >
--
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] Issue Comment Edited: (MRM-1312) mda5 and sha are not
generated for snapshot jars
Posted by "Thorsten Scherler (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207286#action_207286 ]
Thorsten Scherler edited comment on MRM-1312 at 1/18/10 6:50 AM:
-----------------------------------------------------------------
A related observation is when using
mvn deploy:deploy-file -Durl=http://archiva.sadesi.es/repository/snapshots-SADESI \
-DrepositoryId=snapshots-SADESI \
-Dfile=/home/thorsten/.m2/repository/org/apache/cocoon/cocoon-chaperon-impl/1.0.0-SNAPSHOT/cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar \
-DpomFile=/home/thorsten/.m2/repository/org/apache/cocoon/cocoon-chaperon-impl/1.0.0-SNAPSHOT/cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom \
-DgroupId=org.apache.cocoon \
-DartifactId=cocoon -Dversion=1.0.0-SNAPSHOT
the actual file has a unique (timestamp + build number) snapshot version but does not have a file with a -SNAPSHOT in the filename. This way it cannot be resolved later on when resolving the dependencies in our project.
Seems that the "create-missing-checksums consumer" should read the meta information of the artifact and use the latest time stamped version
was (Author: tscherler):
A related observation is when using
mvn deploy:deploy-file -Durl=http://archiva.sadesi.es/repository/snapshots-SADESI \
-DrepositoryId=snapshots-SADESI \
-Dfile=/home/thorsten/.m2/repository/org/apache/cocoon/cocoon-chaperon-impl/1.0.0-SNAPSHOT/cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar \
-DpomFile=/home/thorsten/.m2/repository/org/apache/cocoon/cocoon-chaperon-impl/1.0.0-SNAPSHOT/cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom \
-DgroupId=org.apache.cocoon \
-DartifactId=cocoon -Dversion=6-SNAPSHOT
the actual file has a unique (timestamp + build number) snapshot version but does not have a file with a -SNAPSHOT in the filename. This way it cannot be resolved later on when resolving the dependencies in our project.
Seems that the "create-missing-checksums consumer" should read the meta information of the artifact and use the latest time stamped version
> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
> Key: MRM-1312
> URL: http://jira.codehaus.org/browse/MRM-1312
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Thorsten Scherler
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface.
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar.
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> >
--
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] Updated: (MRM-1312) mda5 and sha are not generated for
snapshot jars
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan updated MRM-1312:
-------------------------------------
Attachment: MRM-1312.patch
Added a patch for this fix with unit test.
Use the actual file, which has a timestamp + build number version, when creating a repository task for a snapshot artifact.
> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
> Key: MRM-1312
> URL: http://jira.codehaus.org/browse/MRM-1312
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Thorsten Scherler
> Fix For: 1.3.1
>
> Attachments: MRM-1312.patch
>
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface.
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar.
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> >
--
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] Commented: (MRM-1312) mda5 and sha are not generated for
snapshot jars
Posted by "Thorsten Scherler (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210217#action_210217 ]
Thorsten Scherler commented on MRM-1312:
----------------------------------------
Ok we tested and the upload issue is fixed but the problem is to download the snapshots. It stores a file with the timestamp but returns a 404 for the snapshot.
> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
> Key: MRM-1312
> URL: http://jira.codehaus.org/browse/MRM-1312
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Thorsten Scherler
> Fix For: 1.3.1
>
> Attachments: MRM-1312.patch
>
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface.
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar.
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> >
--
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] Commented: (MRM-1312) mda5 and sha are not generated for
snapshot jars
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211580#action_211580 ]
Maria Odea Ching commented on MRM-1312:
---------------------------------------
Filed a separate issue for the problem in downloading the snapshots from artifact info page, see MRM-1349. Thanks!
> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
> Key: MRM-1312
> URL: http://jira.codehaus.org/browse/MRM-1312
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Thorsten Scherler
> Assignee: Maria Odea Ching
> Fix For: 1.3.1
>
> Attachments: MRM-1312.patch
>
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface.
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar.
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> >
--
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] Commented: (MRM-1312) mda5 and sha are not generated for
snapshot jars
Posted by "Thorsten Scherler (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207286#action_207286 ]
Thorsten Scherler commented on MRM-1312:
----------------------------------------
A related observation is when using
mvn deploy:deploy-file -Durl=http://archiva.sadesi.es/repository/snapshots-SADESI \
-DrepositoryId=snapshots-SADESI \
-Dfile=/home/thorsten/.m2/repository/org/apache/cocoon/cocoon-chaperon-impl/1.0.0-SNAPSHOT/cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar \
-DpomFile=/home/thorsten/.m2/repository/org/apache/cocoon/cocoon-chaperon-impl/1.0.0-SNAPSHOT/cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom \
-DgroupId=org.apache.cocoon \
-DartifactId=cocoon -Dversion=6-SNAPSHOT
the actual file has a unique (timestamp + build number) snapshot version but does not have a file with a -SNAPSHOT in the filename. This way it cannot be resolved later on when resolving the dependencies in our project.
Seems that the "create-missing-checksums consumer" should read the meta information of the artifact and use the latest time stamped version
> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
> Key: MRM-1312
> URL: http://jira.codehaus.org/browse/MRM-1312
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Thorsten Scherler
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface.
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar.
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> >
--
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