[01/16] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-IT 024d5efb9 -> ef90fe00c (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/0514c1b1 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/0514c1b1 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/0514c1b1 Branch: refs/heads/DEPMGMT-IT Commit: 0514c1b14eadae37c9de77af3ed67ed7388bdf1d Parents: f4e07ac Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Fri Feb 10 22:46:52 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 115 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 484 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/0514c1b1/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..ac38f5d 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult;
[01/10] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-INCLUDE-IT d6cae6167 -> 8690545d9 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/0514c1b1 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/0514c1b1 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/0514c1b1 Branch: refs/heads/DEPMGMT-INCLUDE-IT Commit: 0514c1b14eadae37c9de77af3ed67ed7388bdf1d Parents: f4e07ac Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Fri Feb 10 22:46:52 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 115 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 484 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/0514c1b1/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..ac38f5d 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.Versi
[1/6] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-IMPORT-IT 0b0e5dfaa -> 104e09d94 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/0514c1b1 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/0514c1b1 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/0514c1b1 Branch: refs/heads/DEPMGMT-IMPORT-IT Commit: 0514c1b14eadae37c9de77af3ed67ed7388bdf1d Parents: f4e07ac Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Fri Feb 10 22:46:52 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 115 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 484 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/0514c1b1/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..ac38f5d 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.Version
[1/2] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/MNG-2199-IT f70c03371 -> 22c0bfc01 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/0514c1b1 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/0514c1b1 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/0514c1b1 Branch: refs/heads/MNG-2199-IT Commit: 0514c1b14eadae37c9de77af3ed67ed7388bdf1d Parents: f4e07ac Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Fri Feb 10 22:46:52 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 115 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 484 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/0514c1b1/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..ac38f5d 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult;
[01/15] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT b92cd97aa -> b5c0c75e7 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/0514c1b1 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/0514c1b1 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/0514c1b1 Branch: refs/heads/DEPMGMT Commit: 0514c1b14eadae37c9de77af3ed67ed7388bdf1d Parents: f4e07ac Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Fri Feb 10 22:46:52 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 115 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 484 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/0514c1b1/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..ac38f5d 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /**
[1/9] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-INCLUDE 4f1342800 -> b0b771835 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/0514c1b1 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/0514c1b1 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/0514c1b1 Branch: refs/heads/DEPMGMT-INCLUDE Commit: 0514c1b14eadae37c9de77af3ed67ed7388bdf1d Parents: f4e07ac Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Fri Feb 10 22:46:52 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 115 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 484 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/0514c1b1/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..ac38f5d 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRang
[1/5] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-IMPORT 60df8d378 -> 2f892cba5 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/0514c1b1 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/0514c1b1 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/0514c1b1 Branch: refs/heads/DEPMGMT-IMPORT Commit: 0514c1b14eadae37c9de77af3ed67ed7388bdf1d Parents: f4e07ac Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Fri Feb 10 22:46:52 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 115 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 484 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/0514c1b1/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..ac38f5d 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeR
maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/MNG-2199 283611829 -> 0514c1b14 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/0514c1b1 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/0514c1b1 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/0514c1b1 Branch: refs/heads/MNG-2199 Commit: 0514c1b14eadae37c9de77af3ed67ed7388bdf1d Parents: f4e07ac Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Fri Feb 10 22:46:52 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 115 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 484 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/0514c1b1/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..ac38f5d 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /*
[01/16] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-IT a5faada11 -> 06a682364 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/affddb2e Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/affddb2e Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/affddb2e Branch: refs/heads/DEPMGMT-IT Commit: affddb2e5d1dca0fc956fa61ca60a5843775f94c Parents: 1740265 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sun Feb 5 00:00:31 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 113 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 482 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/affddb2e/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..869e584 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult;
[01/10] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-INCLUDE-IT def336ac6 -> 935c477aa (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/affddb2e Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/affddb2e Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/affddb2e Branch: refs/heads/DEPMGMT-INCLUDE-IT Commit: affddb2e5d1dca0fc956fa61ca60a5843775f94c Parents: 1740265 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sun Feb 5 00:00:31 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 113 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 482 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/affddb2e/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..869e584 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.Versio
[1/6] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-IMPORT-IT c050eceec -> a99fa2d44 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/affddb2e Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/affddb2e Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/affddb2e Branch: refs/heads/DEPMGMT-IMPORT-IT Commit: affddb2e5d1dca0fc956fa61ca60a5843775f94c Parents: 1740265 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sun Feb 5 00:00:31 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 113 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 482 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/affddb2e/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..869e584 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionR
[1/2] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/MNG-2199-IT 26c241c79 -> 37530a4e6 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/affddb2e Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/affddb2e Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/affddb2e Branch: refs/heads/MNG-2199-IT Commit: affddb2e5d1dca0fc956fa61ca60a5843775f94c Parents: 1740265 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sun Feb 5 00:00:31 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 113 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 482 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/affddb2e/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..869e584 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult;
[01/15] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT 2953f94a6 -> f1a1fc6dc (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/affddb2e Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/affddb2e Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/affddb2e Branch: refs/heads/DEPMGMT Commit: affddb2e5d1dca0fc956fa61ca60a5843775f94c Parents: 1740265 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sun Feb 5 00:00:31 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 113 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 482 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/affddb2e/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..869e584 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /**
[1/9] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-INCLUDE 11b79fa8b -> 375e3bb06 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/affddb2e Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/affddb2e Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/affddb2e Branch: refs/heads/DEPMGMT-INCLUDE Commit: affddb2e5d1dca0fc956fa61ca60a5843775f94c Parents: 1740265 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sun Feb 5 00:00:31 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 113 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 482 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/affddb2e/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..869e584 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRange
[1/5] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-IMPORT 7d7c790dc -> 743be82c3 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/affddb2e Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/affddb2e Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/affddb2e Branch: refs/heads/DEPMGMT-IMPORT Commit: affddb2e5d1dca0fc956fa61ca60a5843775f94c Parents: 1740265 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sun Feb 5 00:00:31 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 113 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 482 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/affddb2e/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..869e584 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeRe
maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/MNG-2199 6a243f022 -> affddb2e5 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/affddb2e Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/affddb2e Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/affddb2e Branch: refs/heads/MNG-2199 Commit: affddb2e5d1dca0fc956fa61ca60a5843775f94c Parents: 1740265 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sun Feb 5 00:00:31 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 113 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../maven/project/ProjectModelResolver.java | 1 + .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 30 - .../internal/DefaultModelResolver.java | 1 + 20 files changed, 482 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/affddb2e/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..869e584 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /**
[01/14] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-INCLUDE-IT f127af7ae -> 16ac934fa (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/8229f139 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/8229f139 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/8229f139 Branch: refs/heads/DEPMGMT-INCLUDE-IT Commit: 8229f139502cf9f5cfbb3aea1f60b672d80a6f07 Parents: 1351020 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Mon Jan 30 20:32:39 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 111 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 25 +++- 18 files changed, 473 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/8229f139/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..4241ac2 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /** */ @@ -298,44 +294,6 @@ public class DefaultProjectBuilder boolean localProject;
[01/14] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-INCLUDE 53b92d484 -> f6e3813d0 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/8229f139 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/8229f139 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/8229f139 Branch: refs/heads/DEPMGMT-INCLUDE Commit: 8229f139502cf9f5cfbb3aea1f60b672d80a6f07 Parents: 1351020 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Mon Jan 30 20:32:39 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 111 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 25 +++- 18 files changed, 473 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/8229f139/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..4241ac2 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /** */ @@ -298,44 +294,6 @@ public class DefaultProjectBuilder boolean localProject; -
[01/10] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-IMPORT-IT baa44d221 -> b4c684f27 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/8229f139 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/8229f139 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/8229f139 Branch: refs/heads/DEPMGMT-IMPORT-IT Commit: 8229f139502cf9f5cfbb3aea1f60b672d80a6f07 Parents: 1351020 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Mon Jan 30 20:32:39 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 111 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 25 +++- 18 files changed, 473 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/8229f139/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..4241ac2 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /** */ @@ -298,44 +294,6 @@ public class DefaultProjectBuilder boolean localProject;
[1/9] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/DEPMGMT-IMPORT ebc0d04e9 -> 011207998 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/8229f139 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/8229f139 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/8229f139 Branch: refs/heads/DEPMGMT-IMPORT Commit: 8229f139502cf9f5cfbb3aea1f60b672d80a6f07 Parents: 1351020 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Mon Jan 30 20:32:39 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 111 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 25 +++- 18 files changed, 473 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/8229f139/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..4241ac2 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /** */ @@ -298,44 +294,6 @@ public class DefaultProjectBuilder boolean localProject; -
[1/2] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/MNG-2199-IT ab9324475 -> 60d954499 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/8229f139 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/8229f139 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/8229f139 Branch: refs/heads/MNG-2199-IT Commit: 8229f139502cf9f5cfbb3aea1f60b672d80a6f07 Parents: 1351020 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Mon Jan 30 20:32:39 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 111 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 25 +++- 18 files changed, 473 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/8229f139/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..4241ac2 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /** */ @@ -298,44 +294,6 @@ public class DefaultProjectBuilder boolean localProject; -if
maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/MNG-2199 85e96e3f3 -> 8229f1395 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since 3.2.3 and to remove parent version range resolution logic obsolete since Maven 3.2.3 which changed the initialization of MavenProject instances. o Updated local parent resolution to behave the same way remote parent resolution behaves. When referencing a parent using version ranges, inheriting the version or using version expressions should not be supported. It has been implemented that way for remote parent resolution as it got introduced in Maven 3.2.2. For local parent resolution the version in parent declarations had been ignored completely as of Maven 3.3.0 due to commit be3fb200326208ca4b8c41ebf16d5ae6b8049792 removing all local parent version validation. Work on fixing this is tracked by MNG-5840 released with Maven 3.3.9. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. As an exception, remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/8229f139 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/8229f139 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/8229f139 Branch: refs/heads/MNG-2199 Commit: 8229f139502cf9f5cfbb3aea1f60b672d80a6f07 Parents: 1351020 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Mon Jan 30 20:32:39 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 111 +--- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 25 +++- 18 files changed, 473 insertions(+), 55 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/8229f139/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index d064ab4..4241ac2 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /** */ @@ -298,44 +294,6 @@ public class DefaultProjectBuilder boolean localProject; -if ( req
maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/MNG-2199 944e0806d -> a65b71d5b (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since Maven 3.2.3 and to remove version range resolution logic obsolete since 3.2.3. o Updated to make local and remote parent model resolution consistent when using version ranges. When referencing a parent using version ranges, inheriting the version or using expressions for the project version should not be supported. It has been implemented that way for remote parent resolution from day one. For local parent resolution the version in any parent declarations had been ignored completely. Work on fixing this is tracked by MNG-5840. Commit 40d5087b6b134842e2b61a567dbb4bfbcfab7ae6 got released with Maven 3.3.4. Regressions had been fixed by commits 25f5143169d39075cee67d9f4d11649cce0fafa0 and bd87258629db8e3fcc7aa04777afc16314c3cde0 and released with Maven 3.3.6. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. Remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/a65b71d5 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/a65b71d5 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/a65b71d5 Branch: refs/heads/MNG-2199 Commit: a65b71d5b724947fff4f541cb6dd956576090cda Parents: d413296 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sat Jan 21 18:57:40 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 71 -- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 25 +++- 18 files changed, 435 insertions(+), 53 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/a65b71d5/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index 9d51a6d..e29efa4 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /** */ @@ -298,44 +294,6 @@ public class DefaultProjectBuilder boolean localProject; -if
[1/2] maven git commit: [MNG-2199] Support version ranges in parent elements [Forced Update!]
Repository: maven Updated Branches: refs/heads/MNG-2199-jenkinsfile f47f810f4 -> 9c47113f3 (forced update) [MNG-2199] Support version ranges in parent elements o Updated to fix parent version range resolution broken since Maven 3.2.3 and to remove version range resolution logic obsolete since 3.2.3. o Updated to make local and remote parent model resolution consistent when using version ranges. When referencing a parent using version ranges, inheriting the version or using expressions for the project version should not be supported. It has been implemented that way for remote parent resolution from day one. For local parent resolution the version in any parent declarations had been ignored completely. Work on fixing this is tracked by MNG-5840. Commit 40d5087b6b134842e2b61a567dbb4bfbcfab7ae6 got released with Maven 3.3.4. Regressions had been fixed by commits 25f5143169d39075cee67d9f4d11649cce0fafa0 and bd87258629db8e3fcc7aa04777afc16314c3cde0 and released with Maven 3.3.6. This commit adds the final missing bits to make local and remote parent resolution behave the same way as much as possible. Remote parent resolution still is a bit more strict than local parent resolution due to a different API in use. When resolving a parent from a repository using version ranges, the ModelBuilder verifies the range in use to declare an upper bound. When resolving a parent locally using version ranges, those ranges are not required to declare an upper bound because the API in use does not support querying that. Authoring a POM relying on this difference should be considered a bug. o Added test cases to maven-core testing parent version range resolution for local and remote parent models. Project: http://git-wip-us.apache.org/repos/asf/maven/repo Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/a65b71d5 Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/a65b71d5 Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/a65b71d5 Branch: refs/heads/MNG-2199-jenkinsfile Commit: a65b71d5b724947fff4f541cb6dd956576090cda Parents: d413296 Author: Christian Schulte Authored: Sat Dec 12 20:28:56 2015 +0100 Committer: Christian Schulte Committed: Sat Jan 21 18:57:40 2017 +0100 -- .../maven/project/DefaultProjectBuilder.java| 71 -- .../project/DefaultProjectBuildingRequest.java | 15 ++- .../maven/project/ProjectBuildingRequest.java | 14 +- .../project/AbstractMavenProjectTestCase.java | 11 ++ .../project/DefaultMavenProjectBuilderTest.java | 130 +++ .../repository/TestRepositoryConnector.java | 38 ++ .../org/apache/apache/1/apache-1.pom| 82 .../org/apache/apache/maven-metadata.xml| 13 ++ .../pom.xml | 12 ++ .../pom.xml | 11 ++ .../parent-version-range-external-valid/pom.xml | 11 ++ .../child/pom.xml | 12 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../pom.xml | 7 + .../child/pom.xml | 11 ++ .../parent-version-range-local-valid/pom.xml| 7 + .../model/building/DefaultModelBuilder.java | 25 +++- 18 files changed, 435 insertions(+), 53 deletions(-) -- http://git-wip-us.apache.org/repos/asf/maven/blob/a65b71d5/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java -- diff --git a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java index 9d51a6d..e29efa4 100644 --- a/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java +++ b/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder.java @@ -43,7 +43,6 @@ import org.apache.maven.model.DependencyManagement; import org.apache.maven.model.DeploymentRepository; import org.apache.maven.model.Extension; import org.apache.maven.model.Model; -import org.apache.maven.model.Parent; import org.apache.maven.model.Plugin; import org.apache.maven.model.Profile; import org.apache.maven.model.ReportPlugin; @@ -73,9 +72,6 @@ import org.eclipse.aether.repository.RemoteRepository; import org.eclipse.aether.repository.WorkspaceRepository; import org.eclipse.aether.resolution.ArtifactRequest; import org.eclipse.aether.resolution.ArtifactResult; -import org.eclipse.aether.resolution.VersionRangeRequest; -import org.eclipse.aether.resolution.VersionRangeResolutionException; -import org.eclipse.aether.resolution.VersionRangeResult; /** */ @@ -298,44 +294,6 @@ public class DefaultProjectBuilder boolean loc
