You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Jason Chaffee (JIRA)" <ji...@codehaus.org> on 2008/04/09 00:54:58 UTC
[jira] Created: (MRM-772) metatadata-updater should update all
sections of the metadata file, if there is something not correct
metatadata-updater should update all sections of the metadata file, if there is something not correct
-----------------------------------------------------------------------------------------------------
Key: MRM-772
URL: http://jira.codehaus.org/browse/MRM-772
Project: Archiva
Issue Type: Improvement
Components: repository scanning
Affects Versions: 1.0.2
Reporter: Jason Chaffee
Priority: Critical
According to the documentation the metadata-updater will do the
following:
metadata-updater - Updates artifact metadata files depending on the content of the repository.
I have been testing this by deploying several artifacts to the repository and getting a specific timestamp and build number in the maven-metatadata.xml file. Next, I delete the latest (snapshot) build from the repo, including checksums. I run the repository scanner and the database-updater and this file is never fixed based on the actual contents of the file system. Archive updates it internal metadata, but not maven's metadata and thus maven fails to download the artifact.
>From Brett:
I think at present the updater corrects the <versions> flag, but not the snapshot information (it also doesn't correct the plugin group metadata).
--
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-772) metatadata-updater should update all
sections of the metadata file, if there is something not correct
Posted by "Jason Chaffee (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130206#action_130206 ]
Jason Chaffee commented on MRM-772:
-----------------------------------
If I "touch" the artifacts that remain on the file system after deleting, then it will update the metadata file correctly.
However, it would be better if it updates this regardless of the other artifacts being touched because we would prefer that the file system timestamp be the same as the actual deploy timestamp and touching would change this and make it a little more confusing for someone looking at the file system.
> metatadata-updater should update all sections of the metadata file, if there is something not correct
> -----------------------------------------------------------------------------------------------------
>
> Key: MRM-772
> URL: http://jira.codehaus.org/browse/MRM-772
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.0.2
> Reporter: Jason Chaffee
> Priority: Critical
>
> According to the documentation the metadata-updater will do the
> following:
> metadata-updater - Updates artifact metadata files depending on the content of the repository.
> I have been testing this by deploying several artifacts to the repository and getting a specific timestamp and build number in the maven-metatadata.xml file. Next, I delete the latest (snapshot) build from the repo, including checksums. I run the repository scanner and the database-updater and this file is never fixed based on the actual contents of the file system. Archive updates it internal metadata, but not maven's metadata and thus maven fails to download the artifact.
> From Brett:
> I think at present the updater corrects the <versions> flag, but not the snapshot information (it also doesn't correct the plugin group metadata).
--
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-772) metatadata-updater does not recognise
deleted files when updating snapshot version metadata
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay updated MRM-772:
------------------------------------
Fix Version/s: (was: 1.1.x)
1.2
Moving to 1.2
> metatadata-updater does not recognise deleted files when updating snapshot version metadata
> -------------------------------------------------------------------------------------------
>
> Key: MRM-772
> URL: http://jira.codehaus.org/browse/MRM-772
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.0.2
> Reporter: Jason Chaffee
> Priority: Critical
> Fix For: 1.2
>
>
> According to the documentation the metadata-updater will do the
> following:
> metadata-updater - Updates artifact metadata files depending on the content of the repository.
> I have been testing this by deploying several artifacts to the repository and getting a specific timestamp and build number in the maven-metatadata.xml file. Next, I delete the latest (snapshot) build from the repo, including checksums. I run the repository scanner and the database-updater and this file is never fixed based on the actual contents of the file system. Archive updates it internal metadata, but not maven's metadata and thus maven fails to download the artifact.
> From Brett:
> I think at present the updater corrects the <versions> flag, but not the snapshot information (it also doesn't correct the plugin group metadata).
--
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-772) metatadata-updater should update all
sections of the metadata file, if there is something not correct
Posted by "Jason Chaffee (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130204#action_130204 ]
Jason Chaffee commented on MRM-772:
-----------------------------------
For example, here is the latest artifact on the file system:
test-1.0-2008407.211352-3.jar
here is the metatdata file:
<metadata>
<groupId>chaffee.jason.test</groupId>
<artifactId>test</artifactId>
<version>1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<buildNumber>5</buildNumber>
<timestamp>20080407.212453</timestamp>
</snapshot>
<lastUpdated>20080407212454</lastUpdated>
</versioning>
</metadata>
> metatadata-updater should update all sections of the metadata file, if there is something not correct
> -----------------------------------------------------------------------------------------------------
>
> Key: MRM-772
> URL: http://jira.codehaus.org/browse/MRM-772
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.0.2
> Reporter: Jason Chaffee
> Priority: Critical
>
> According to the documentation the metadata-updater will do the
> following:
> metadata-updater - Updates artifact metadata files depending on the content of the repository.
> I have been testing this by deploying several artifacts to the repository and getting a specific timestamp and build number in the maven-metatadata.xml file. Next, I delete the latest (snapshot) build from the repo, including checksums. I run the repository scanner and the database-updater and this file is never fixed based on the actual contents of the file system. Archive updates it internal metadata, but not maven's metadata and thus maven fails to download the artifact.
> From Brett:
> I think at present the updater corrects the <versions> flag, but not the snapshot information (it also doesn't correct the plugin group metadata).
--
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-772) metatadata-updater does not recognise
deleted files when updating snapshot version metadata
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-772:
-----------------------------
Summary: metatadata-updater does not recognise deleted files when updating snapshot version metadata (was: metatadata-updater should update all sections of the metadata file, if there is something not correct)
> metatadata-updater does not recognise deleted files when updating snapshot version metadata
> -------------------------------------------------------------------------------------------
>
> Key: MRM-772
> URL: http://jira.codehaus.org/browse/MRM-772
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.0.2
> Reporter: Jason Chaffee
> Priority: Critical
> Fix For: 1.0.x
>
>
> According to the documentation the metadata-updater will do the
> following:
> metadata-updater - Updates artifact metadata files depending on the content of the repository.
> I have been testing this by deploying several artifacts to the repository and getting a specific timestamp and build number in the maven-metatadata.xml file. Next, I delete the latest (snapshot) build from the repo, including checksums. I run the repository scanner and the database-updater and this file is never fixed based on the actual contents of the file system. Archive updates it internal metadata, but not maven's metadata and thus maven fails to download the artifact.
> From Brett:
> I think at present the updater corrects the <versions> flag, but not the snapshot information (it also doesn't correct the plugin group metadata).
--
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-772) metatadata-updater does not recognise
deleted files when updating snapshot version metadata
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-772:
-----------------------------
Fix Version/s: 1.0.x
> metatadata-updater does not recognise deleted files when updating snapshot version metadata
> -------------------------------------------------------------------------------------------
>
> Key: MRM-772
> URL: http://jira.codehaus.org/browse/MRM-772
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.0.2
> Reporter: Jason Chaffee
> Priority: Critical
> Fix For: 1.0.x
>
>
> According to the documentation the metadata-updater will do the
> following:
> metadata-updater - Updates artifact metadata files depending on the content of the repository.
> I have been testing this by deploying several artifacts to the repository and getting a specific timestamp and build number in the maven-metatadata.xml file. Next, I delete the latest (snapshot) build from the repo, including checksums. I run the repository scanner and the database-updater and this file is never fixed based on the actual contents of the file system. Archive updates it internal metadata, but not maven's metadata and thus maven fails to download the artifact.
> From Brett:
> I think at present the updater corrects the <versions> flag, but not the snapshot information (it also doesn't correct the plugin group metadata).
--
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