Version ranges in maven are very buggy, use with caution. Dave - sent via G1
On May 11, 2009 4:23 PM, "KurtG" <[email protected]> wrote: This should look familiar ----------- [INFO] Failed to resolve artifact. No versions are present in the repository for the artifact with a range [2.1,) commons-collections:commons-collections:jar:null from the specified remote repositories: central (http://repo1.maven.org/maven2) Path to dependency: 1) my.xxx.company.SideScanProxy:jar:3.1-snapshot 2) jasperreports:jasperreports:jar:1.3.0 -------------- And, the dependency came from jasperreports: <dependency> <groupId>commons-collections</groupId> <artifactId>commons-collections</artifactId> <version>[2.1,)</version> <scope>compile</scope> </dependency> but, if you look here: http://repo2.maven.org/maven2/commons-collections/commons-collections/ There are a number of versions with 2.1 and higher that all contain jars. Hm? What's up? -- View this message in context: http://www.nabble.com/Newbie---Can%27t-resolve-artifact.-tp23492610p23492610.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
