You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristoffer Peterhäesel (JIRA)" <ji...@codehaus.org> on 2011/02/08 15:25:22 UTC
[jira] Created: (MNG-5006) M3 attempts to get released parent pom
from snapshot repository when a dependency has range
M3 attempts to get released parent pom from snapshot repository when a dependency has range
-------------------------------------------------------------------------------------------
Key: MNG-5006
URL: http://jira.codehaus.org/browse/MNG-5006
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.0.2
Environment: WinXP SP3, Java 6u20
Reporter: Kristoffer Peterhäesel
Attachments: mvn-verify-fixed-version.log, mvn-verify-range-version.log
I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released parent pom
from snapshot repository when a dependency has range
Posted by "Sei Syvalta (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sei Syvalta updated MNG-5006:
-----------------------------
Attachment: maven-version-range-test2.zip
Previous version didn't work with a clean repo. Needed to change the range from [1.0,2.0) to [1.0-SNAPSHOT,2.0).
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Attachments: maven-version-range-test.zip, maven-version-range-test2.zip, mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released parent pom
from snapshot repository when a dependency has range
Posted by "Sei Syvalta (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sei Syvalta updated MNG-5006:
-----------------------------
Attachment: maven-version-range-test.zip
Very simple test to reproduce the error. Build module a first and then b. Building b should fail.
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Attachments: maven-version-range-test.zip, mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released parent pom
from snapshot repository when a dependency has range
Posted by "Kristoffer Peterhansel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257422#action_257422 ]
Kristoffer Peterhansel commented on MNG-5006:
---------------------------------------------
Nice work. Didn't think it would be so easy to reproduce =)
Instead of cleaning the repo you can just use another one. Running Maven on these projects with an option like "-Dmaven.repo.local=..\repo" will do it for me.
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Attachments: maven-version-range-test.zip, maven-version-range-test2.zip, mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) [regression] Resolution of parent POMs
for dependency using version range does not consider all configured
repositories
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-5006:
-----------------------------------
Summary: [regression] Resolution of parent POMs for dependency using version range does not consider all configured repositories (was: M3 attempts to get released parent pom from snapshot repository when a dependency has range)
> [regression] Resolution of parent POMs for dependency using version range does not consider all configured repositories
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Attachments: maven-version-range-test.zip, maven-version-range-test2.zip, mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released parent pom
from snapshot repository when a dependency has range
Posted by "Kristoffer Peterhäesel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255075#action_255075 ]
Kristoffer Peterhäesel commented on MNG-5006:
---------------------------------------------
I forgot to mention one thing - since it is not obvious. But in this case it seems to be the parent of the dependency with the version range (coreapis in this case) that is being checked. Not the parent of the project we are running maven against.
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhäesel
> Attachments: mvn-verify-fixed-version.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released parent pom
from snapshot repository when a dependency has range
Posted by "Kristoffer Peterhäesel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristoffer Peterhäesel updated MNG-5006:
----------------------------------------
Attachment: mvn-verify-offline.log
Just tried to do the same with the -o option. And interestingly enough it appears to still try to validate the masterproject pom against the snapshot repository. And it still fails with the 'excuse' that is cannot resolve it. Hard to accept since it finds it just fine as the parent of the project of the pom maven is running against - or it would fail much sooner.
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhäesel
> Attachments: mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) [regression] Resolution of parent POMs
for dependency using version range does not consider all configured
repositories
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-5006.
----------------------------------
Resolution: Fixed
Assignee: Benjamin Bentmann
Fixed in [r1074131|http://svn.apache.org/viewvc?view=revision&revision=1074131], thanks for the example project.
> [regression] Resolution of parent POMs for dependency using version range does not consider all configured repositories
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Assignee: Benjamin Bentmann
> Fix For: 3.0.3
>
> Attachments: maven-version-range-test.zip, maven-version-range-test2.zip, mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released parent pom
from snapshot repository when a dependency has range
Posted by "Sei Syvalta (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256772#action_256772 ]
Sei Syvalta commented on MNG-5006:
----------------------------------
Adding my post to the user list here too:
I'm running into this too. I tried to create a test project but unfortunately the problem didn't reproduce there.
Some background:
- dependency to artifact with version range [1.0.1, 2.0), matching versions [1.0.1, 1.0.2, 1.0.3-SNAPSHOT].
- problems occurs when 1.0.3-SNAPSHOT tries to load it's _released_ parent pom.
- if parent of 1.0.3-SNAPSHOT is changed to a snapshot the build succeeds.
Some observations:
- when SNAPSHOT is resolved from local repository it's list of repositories is empty. Also when it's parent is resolved it's list of repositories is empty.
- org.apache.maven.model.building.DefaultModelBuilder.readParentExternally fails because of that (no repositories)
- parent is not found from local repository because the key in repo tracking properties is "test-parent-pom-1.0.1.pom>releases" but is searched with key "test-parent-pom-1.0.1.pom>".
Stack trace from one point of execution:
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(org.sonatype.aether.RepositorySystemSession, java.util.Collection<? extends org.sonatype.aether.resolution.ArtifactRequest>) line: 237
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(org.sonatype.aether.RepositorySystemSession, org.sonatype.aether.resolution.ArtifactRequest) line: 214
org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(java.lang.String, java.lang.String, java.lang.String) line: 115
org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(org.apache.maven.model.Model, org.apache.maven.model.building.ModelBuildingRequest, org.apache.maven.model.building.DefaultModelProblemCollector) line: 819
org.apache.maven.model.building.DefaultModelBuilder.readParent(org.apache.maven.model.Model, org.apache.maven.model.building.ModelBuildingRequest, org.apache.maven.model.building.DefaultModelProblemCollector) line: 670
org.apache.maven.model.building.DefaultModelBuilder.build(org.apache.maven.model.building.ModelBuildingRequest, java.util.Collection<java.lang.String>) line: 308
org.apache.maven.model.building.DefaultModelBuilder.build(org.apache.maven.model.building.ModelBuildingRequest) line: 232
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(org.sonatype.aether.RepositorySystemSession, org.sonatype.aether.resolution.ArtifactDescriptorRequest, org.sonatype.aether.resolution.ArtifactDescriptorResult) line: 308
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(org.sonatype.aether.RepositorySystemSession, org.sonatype.aether.resolution.ArtifactDescriptorRequest) line: 173
org.sonatype.aether.impl.internal.DefaultDependencyCollector.process(org.sonatype.aether.RepositorySystemSession, org.sonatype.aether.collection.CollectResult, java.util.LinkedList<org.sonatype.aether.impl.internal.GraphEdge>, java.util.List<org.sonatype.aether.graph.Dependency>, java.util.List<org.sonatype.aether.repository.RemoteRepository>, org.sonatype.aether.collection.DependencySelector, org.sonatype.aether.collection.DependencyManager, org.sonatype.aether.collection.DependencyTraverser, org.sonatype.aether.impl.internal.DataPool) line: 419
org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(org.sonatype.aether.RepositorySystemSession, org.sonatype.aether.collection.CollectRequest) line: 233
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Attachments: mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released
parent pom from snapshot repository when a dependency has range
Posted by "Sei Syvalta (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256775#action_256775 ]
Sei Syvalta edited comment on MNG-5006 at 2/18/11 7:48 AM:
-----------------------------------------------------------
{quote}
- org.apache.maven.model.building.DefaultModelBuilder.readParentExternally fails because of that (no repositories)
- parent is not found from local repository because the key in repo tracking properties is "test-parent-pom-1.0.1.pom>releases" but is searched with key "test-parent-pom-1.0.1.pom>".{quote}
The difference to the working direct SNAPSHOT reference (i.e. non-range) is the list of repositories. The local repo lookup fails also in that case, but parent will be found from remote repo.
was (Author: bugittaa):
> org.apache.maven.model.building.DefaultModelBuilder.readParentExternally fails because of that (no repositories)
> parent is not found from local repository because the key in repo tracking properties is "test-parent-pom-1.0.1.pom>releases" but is searched with key "test-parent-pom-1.0.1.pom>".
The difference to the working direct SNAPSHOT reference (i.e. non-range) is the list of repositories. The local repo lookup fails also in that case, but parent will be found from remote repo.
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Attachments: mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) [regression] Resolution of parent POMs
for dependency using version range does not consider all configured
repositories
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-5006:
-----------------------------------
Fix Version/s: 3.0.3
> [regression] Resolution of parent POMs for dependency using version range does not consider all configured repositories
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Fix For: 3.0.3
>
> Attachments: maven-version-range-test.zip, maven-version-range-test2.zip, mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released
parent pom from snapshot repository when a dependency has range
Posted by "Sei Syvalta (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257417#action_257417 ]
Sei Syvalta edited comment on MNG-5006 at 2/23/11 5:32 AM:
-----------------------------------------------------------
Very simple test to reproduce the error. Build module a first and then b. Building b should fail. If not try cleaning local repo and try again.
was (Author: bugittaa):
Very simple test to reproduce the error. Build module a first and then b. Building b should fail.
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Attachments: maven-version-range-test.zip, mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released parent pom
from snapshot repository when a dependency has range
Posted by "Sei Syvalta (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256775#action_256775 ]
Sei Syvalta commented on MNG-5006:
----------------------------------
> org.apache.maven.model.building.DefaultModelBuilder.readParentExternally fails because of that (no repositories)
> parent is not found from local repository because the key in repo tracking properties is "test-parent-pom-1.0.1.pom>releases" but is searched with key "test-parent-pom-1.0.1.pom>".
The difference to the working direct SNAPSHOT reference (i.e. non-range) is the list of repositories. The local repo lookup fails also in that case, but parent will be found from remote repo.
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhansel
> Attachments: mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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-5006) M3 attempts to get released parent pom
from snapshot repository when a dependency has range
Posted by "Kristoffer Peterhäesel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255953#action_255953 ]
Kristoffer Peterhäesel commented on MNG-5006:
---------------------------------------------
I just realized that this works just fine on our Hudson server. So it seems like it could be some sort of environment thing. But they use the same identical settings.xml . The only differences I can think of is that it is running JDK 6u17 and Windows 2003 R2
> M3 attempts to get released parent pom from snapshot repository when a dependency has range
> -------------------------------------------------------------------------------------------
>
> Key: MNG-5006
> URL: http://jira.codehaus.org/browse/MNG-5006
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: WinXP SP3, Java 6u20
> Reporter: Kristoffer Peterhäesel
> Attachments: mvn-verify-fixed-version.log, mvn-verify-offline.log, mvn-verify-range-version.log
>
>
> I have a bit of a strange issue. When running under Maven 3.0.2 I am getting build errors when I try to build one of our projects when one of their dependencies have a range version. But when setting it to a specific version it seems to work. The same project works without a hitch in Maven 2.2.1.
> As can be seen from the first included verbose trace (mvn-verify-range-version.log). Maven attempts to get the pom from our snapshot repository. That will, obviously, not work for a released artefact.
> Changing the dependency version from the [1,2) range to 1.0.1-SNAPSHOT seems to skip that step completely. Even though it resolves to the same version in the end. As seen in the other verbose trace (mvn-verify-fixed-version.log)
--
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