Hi all, I have a doubt with dependencies using version ranges. Here:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges It says: "Incorporating SNAPSHOT versions into the specification Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary. There is no need to compile against development code unless you are explicitly using a new feature, under which the snapshot will become the lower bound of your version specification. As releases are considered newer than the snapshot they belong to, they will be chosen over an old snapshot if found. It is possible that applications such as Continuum may have a mode that enables always resolving to the snapshot version, but this is external to the POM itself." But I'm not sure whether it's an implemented feature or not. I have a POM with a dependency: <dependency> <groupId>com.digibis</groupId> <artifactId>digisqlhib</artifactId> <version>[1.3, ]</version> <optional></optional> </dependency> But when I try to run a relese:prepare, I get this output: [INFO] Can't release project due to non released dependencies : com.digibis:digisqlhib:jar:1.4-SNAPSHOT:compile Is there a way to avoid snapshots in version ranges? Am I doing something wrong?. I'm using Maven 2.0.4 and I have separate repositories for releases and snapshots. Thanks in advance, [Akbarr]
