x.y.z-alphanumeric < x.y.z < x.y.z-numeric
and x.y.z-A < x.y.z-B where A is before B in the alphabeth.
This was triggered by a user question on the dev list, and took unit
tests to answer the question - committing as 'documentation'.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@414014 13f79535-47bb-0310-9956-ffa450edef68
plugin manager and the extension manger. now used in the extension manager to block out
deps that are already present in the maven classloading system. so that something like
the external provider can be listed in an extension and will be dealt with: this was
causing a loader constraint violation.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@368218 13f79535-47bb-0310-9956-ffa450edef68
Submitted By: Edwin Punzalan
Reviewed By: John Casey
Applied patches, with minor changes.
These patches will ensure that the optional flag is passed on and inherited correctly when dealing with managed dependencies.
I changed the patches, in that I added a new createDependencyArtifact(..) method on ArtifactFactory, which will eliminate the need to call an older variant of the method by passing in a null value for the inheritedScope parameter.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@354544 13f79535-47bb-0310-9956-ffa450edef68
Submitted By: John Casey
Prevent the artifact collector from firing an inclusion event when the node is disabled. In this case, the node will not be included in any subsequent classpath, so firing an inclusion/selection event is incorrect.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@348473 13f79535-47bb-0310-9956-ffa450edef68
o Disabled version-range checking for system-scoped dependencies...will use recommendedVersion where available, if a concrete version is not available.
o Disabled collection of the transitive deps of a system-scoped dep.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@332220 13f79535-47bb-0310-9956-ffa450edef68
o Fixed unit test for resolving direct optional dependencies.
o Added isChildOfRootNode() method in ResolutionNode, to check whether the parent node's parent is null.
o Added check in the artifact collector to include optional artifacts if they are direct dependencies of the root node.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@332213 13f79535-47bb-0310-9956-ffa450edef68
Submitted By: Piotr Bzdyl
Reviewed By: John Casey
Applied portions of the patch that pertained to the lifecycle mappings and artifact handlers for ejb3/par. The implementations of these plugins is in the sandbox (or soon will be).
Thanks for the patch, Piotr!
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@332151 13f79535-47bb-0310-9956-ffa450edef68
Submitted By: Jerome Lacoste
Reviewed By: John Casey
I did not apply this patch. A better solution was to initialize the artifact data a little more thoroughly, and only delegate those methods which must track changes to the main artifact (like version info, groupId, and artifactId...essentially, the things that determine how to locate metadata on the repository). For these delegating methods, I've disabled the corresponding setter methods with UnsupportedOperationException to indicate that these attributes must be managed via the main artifact, and why. The MavenProjectHelper will now lookup the proper ArtifactHandler for the given attachment type, and pass that on to the AttachedArtifact constructor also.
Jerome, thanks very much for the effort in exploring this issue. I appreciate the help.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@330392 13f79535-47bb-0310-9956-ffa450edef68
Added ArtifactFactory.cloneArtifact(..) +implementation, and made MavenProject(MavenProject) use that to create a copy of the project's artifact.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@330080 13f79535-47bb-0310-9956-ffa450edef68
John Dennis Casey
Carlos Sanchez Gonzalez
Kenney Westerhof
Brett Leslie Porter
Jason van Zyl