lets say if "x.y.z.w" represents a path in a version tree, then specifying "x.y.z.*" as dependency version should mean dependency resolution only within the leafs of "z". my organization is not satisfied with linear "ranges" for dependency resolution and they want a "tree-based" instead (which to my opinion is definitely more accurate and fruitful than maven default).
introducing this feature basically means rewriting project.MavenMetadataSource.createArtifacts(...) method, or correct me if i'm wrong (i assume that it's not the dependency-plugin which resolves and downloads dependencies by default). the implementation is very simple, but the integration - not at all (we all love static methods :P). so i wonder if there's another way besides building maven core manually? -- View this message in context: http://www.nabble.com/extending-version-range-spec-tp21175150p21175150.html Sent from the Maven Developers mailing list archive at Nabble.com.
