2008/12/17 Bracewell, Robert <[email protected]> > Hi, > > Do version ranges work across Maven plugins or are they limited to Maven > core functionality? > As an example I defined a dependency with a range of <version> > [4.4.2.01,)</version> and all was well. But when I tried to use the same > notation with the maven-dependency-plugin 2.0 it results in a fatal error > stating that version was null for the groupId:artifactId > > Is there a way around this with ranges or do I have to resort to ensuring > that versions are explicitly stated? > > Thanks, > Robert >
This is not an answer to your question, but a suggestion for a work-around. If a plugin does not support version ranges, you can always use the versions-maven-plugin's update-properties goal to populate a property from a version range... of course as the versions-maven-plugin modifies the pom, the changes will not be picked up within the reactor, so you'd have to run it as a separate invokation of maven prior to your build. But you should also file a JIRA against the plugin that is not supporting version ranges. When filing a JIRA, it helps if you can provide a sample project that reproduces the issue. -Stephen
