You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Pavel Halas (JIRA)" <ji...@codehaus.org> on 2007/02/22 11:19:27 UTC
[jira] Created: (MNG-2839) Non-unique-version snapshots not updated
Non-unique-version snapshots not updated
----------------------------------------
Key: MNG-2839
URL: http://jira.codehaus.org/browse/MNG-2839
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.5
Reporter: Pavel Halas
Test case:
- let's have a repository with [uniqueVersion]false[/uniqueVersion].
- let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
- go to your local repository and change the file content. You can also remove all the metadata.
- run "mvn -U" on your project
- you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
- the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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: (MNG-2839) Non-unique-version snapshots not updated
Posted by "Pavel Halas (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Halas updated MNG-2839:
-----------------------------
Attachment: dep-update.zip
Sample projects.
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
> Assignee: Brett Porter
> Fix For: 2.0.x
>
> Attachments: dep-update.zip
>
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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: (MNG-2839) Non-unique-version snapshots not updated
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-2839:
------------------------------
Assignee: Brett Porter
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.0.x
Component/s: Artifacts and Repositories
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
> Assignee: Brett Porter
> Fix For: 2.0.x
>
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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: (MNG-2839) Non-unique-version
snapshots not updated
Posted by "Pavel Halas (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99623 ]
Pavel Halas edited comment on MNG-2839 at 6/15/07 10:45 AM:
------------------------------------------------------------
Sample projects.
How to use it:
- deploy the dep1 project into a repository with non-unique version setup.
- work with the test project (like c:/temp/test/> mvn package)
- change the local repository content of the dep1-1.0-SNAPSHOT.jar
- enforce updating the dependencies (like c:/temp/test/> mvn package -U)
- check the dep1-1.0-SNAPSHOT.jar local repository content. Sometimes the remote repository version is not used.
was:
Sample projects.
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
> Assignee: Brett Porter
> Fix For: 2.0.x
>
> Attachments: dep-update.zip
>
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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: (MNG-2839) Non-unique-version
snapshots not updated
Posted by "Pavel Halas (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93312 ]
Pavel Halas edited comment on MNG-2839 at 4/18/07 9:13 AM:
-----------------------------------------------------------
Yes. It's the hardcore use case. Nevertheless, it fails to update it (without such manual changes) in regular update cycle (based on settings.xml) too.
was:
Yes. It's the hardcore use case. Nevertheless, it fails to update it in regular update cycle (based on settings.xml) too.
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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-2839) Non-unique-version snapshots not updated
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-2839.
----------------------------------
Resolution: Won't Fix
Fix Version/s: (was: Issues to be reviewed for 3.x)
Assignee: Benjamin Bentmann
As per MNG-4059, non-unique snapshots are no longer supported.
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
> Assignee: Benjamin Bentmann
> Attachments: dep-update.zip
>
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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-2839) Non-unique-version snapshots not
updated
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93311 ]
Brian Fox commented on MNG-2839:
--------------------------------
Not sure I understand. You're saying that you changed the file in your local repo and then you expect it to update again from the repo?
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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: (MNG-2839) Non-unique-version snapshots not updated
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-2839:
------------------------------
Assignee: (was: Brett Porter)
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
> Fix For: 2.2.x (to be reviewed)
>
> Attachments: dep-update.zip
>
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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-2839) Non-unique-version snapshots not
updated
Posted by "Pavel Halas (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93312 ]
Pavel Halas commented on MNG-2839:
----------------------------------
Yes. It's the hardcore use case. Nevertheless, it fails to update it in regular update cycle (based on settings.xml) too.
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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-2839) Non-unique-version snapshots not
updated
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99620 ]
Brett Porter commented on MNG-2839:
-----------------------------------
please provide the sample project you refer to so we can be sure we are talking about the same thing. MNG-1908 was certainly fixed according to the tests cases given.
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
> Assignee: Brett Porter
> Fix For: 2.0.x
>
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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