On Fri, Feb 11, 2011 at 3:56 PM, Benjamin Bentmann <[email protected]> wrote: > Vidar Ramdal wrote: > >> Could you elaborate on this? Does it mean that<latest> is some kind >> of internal Maven stuff that cannot be relied on? > > Exactly, it supports automatic plugin version resolution.
So <latest> is only used for plugins, if I understand correctly. Good to know. >> Unfortunately it doesn't work for me (could be an issue with >> maven-launchpad-plugin). >> I'm getting this when building: >> java.lang.NullPointerException: version was null for >> com.idium.kolibri:kolibri-cache-util >> at >> org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) >> at >> org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout.pathOf(DefaultRepositoryLayout.java:47) >> at >> org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOf(DefaultArtifactRepository.java:110) >> at >> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:141) >> at >> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90) >> at >> org.apache.sling.maven.projectsupport.AbstractBundleListMojo.getArtifact(AbstractBundleListMojo.java:196) > > You need to resolve a version range first and pick a specific version before > trying to resolve an artifact. IIRC, it was something along the lines of > MavenMetadataSource.retrieveAvailableVersions() followed by a call to > VersionRange.matchVersion() to select the version. I'll report this as an issue against maven-launchpad-plugin. Thanks for your help! -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 Quando omni flunkus moritatus! --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
