The dependency:copy/unpack goals don't work with ranges and probably won't since replicating it is a huge mess. Instead, declare the artifact as a dependency and use copy-dependencies/unpack-dependencies along with some include/exclude filters in the config and it will do the same thing.
-----Original Message----- From: Bracewell, Robert [mailto:rbrac...@qualcomm.com] Sent: Wednesday, December 17, 2008 2:44 AM To: users@maven.apache.org Subject: Version ranges 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
