You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/12/23 13:21:57 UTC
[jira] Created: (MNG-4952) [regression] RELEASE field of repository
metadata is not updated upon repeated deployments
[regression] RELEASE field of repository metadata is not updated upon repeated deployments
------------------------------------------------------------------------------------------
Key: MNG-4952
URL: http://jira.codehaus.org/browse/MNG-4952
Project: Maven 2 & 3
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0.1
Reporter: Benjamin Bentmann
As reported by [Marcin Kuthan on the user list|http://www.mail-archive.com/users@maven.apache.org/msg115404.html], the g:a-level metadata's release field is not updated upon redeployments, i.e. the value is stuck at its initial value.
--
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: (MNG-4952) [regression] RELEASE field of repository
metadata is not updated upon repeated deployments
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4952.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.2
Assignee: Benjamin Bentmann
Fixed in [r1054683|http://svn.apache.org/viewvc?view=revision&revision=1054683].
> [regression] RELEASE field of repository metadata is not updated upon repeated deployments
> ------------------------------------------------------------------------------------------
>
> Key: MNG-4952
> URL: http://jira.codehaus.org/browse/MNG-4952
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0.1
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0.2
>
>
> As reported by [Marcin Kuthan on the user list|http://www.mail-archive.com/users@maven.apache.org/msg115404.html], the g:a-level metadata's release field is not updated upon redeployments, i.e. the value is stuck at its initial value.
--
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: (MNG-4952) [regression] RELEASE field of
repository metadata is not updated upon repeated deployments
Posted by "Frank Prumbaum (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260042#action_260042 ]
Frank Prumbaum commented on MNG-4952:
-------------------------------------
I can confirm the fix in 3.0.3.
What is still not updated is the LATEST-Tag.
Our problem with this is the Nexus-repository manager, because there the LATEST-Tag is inserted when you (re-)create maven metadata (v.1.9.0.1).
We deploy your software querying nexus with the v=LATEST parameter which takes into account the RELEASE and LATEST-Tag. If maven never updates LATEST but nexus does, we can never be sure what version will be deployed. What is sonatype's strategy on this type of metadata?
> [regression] RELEASE field of repository metadata is not updated upon repeated deployments
> ------------------------------------------------------------------------------------------
>
> Key: MNG-4952
> URL: http://jira.codehaus.org/browse/MNG-4952
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0.1
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0.2
>
>
> As reported by [Marcin Kuthan on the user list|http://www.mail-archive.com/users@maven.apache.org/msg115404.html], the g:a-level metadata's release field is not updated upon redeployments, i.e. the value is stuck at its initial value.
--
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: (MNG-4952) [regression] RELEASE field of
repository metadata is not updated upon repeated deployments
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260044#action_260044 ]
Benjamin Bentmann commented on MNG-4952:
----------------------------------------
LATEST is only ever used for plugins. This metaversion is an internal impl detail, ordinary dependency resolution should use version ranges.
> [regression] RELEASE field of repository metadata is not updated upon repeated deployments
> ------------------------------------------------------------------------------------------
>
> Key: MNG-4952
> URL: http://jira.codehaus.org/browse/MNG-4952
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0.1
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0.2
>
>
> As reported by [Marcin Kuthan on the user list|http://www.mail-archive.com/users@maven.apache.org/msg115404.html], the g:a-level metadata's release field is not updated upon redeployments, i.e. the value is stuck at its initial value.
--
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