Ok. I'll file a bug with an example.
Ørjan Brett Porter wrote:
It is supported - this should work (and if there is a reason it couldn't find a version, it should report a better message). This is a bug. - Brett On 9/22/05, Orjan Austvold <[EMAIL PROTECTED]> wrote:In an eager attempt I came to specify a couple of dependencies in a parent-pom of a plugin as <dependency> <groupId>org.apache.maven</groupId> <artifactId>maven-project</artifactId> <version>[2.0-beta-1,)</version> </dependency> <dependency> <groupId>org.apache.maven</groupId> <artifactId>maven-plugin-api</artifactId> <version>[2.0-beta-1,)</version> </dependency> After some fiddling I found out that this was the reason for a NPE in my build. java.lang.NullPointerException: version was null for org.apache.maven:maven-plugin-api at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:311) at org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:208) ... I could not find any information on the maven2 site about ranged deps so I guess they are not supported (yet)? Best regards, Ørjan -- Ørjan Austvold - Senior Software Architect www.colibria.com - putting the presence into messaging --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
