> On Feb 7, 2011, at 9:49 AM, Vidar Ramdal <[email protected]> wrote: >> Hi, I'm trying to set up a build that will always use the latest >> snapshot of our in-house bundles. >> >> Thus, I'm specifying <version>LATEST</version> in the bundle list XML file: >> <bundle> >> <groupId>com.idium.kolibri</groupId> >> <artifactId>kolibri-loginmodule</artifactId> >> <version>LATEST</version> >> </bundle> >> >> The build fails constantly with "Embedded error: Unable to determine >> the latest version" (see full stacktrace below). >> >> Is this supposed to work with the Launchpad plugin? >> [...]
On Tue, Feb 8, 2011 at 1:38 AM, Justin Edelson <[email protected]> wrote: > The plugin uses the normal Maven artifact resolution subsystem, so it should > work. We use RELEASE as the http service version. > > I personally don't use LATEST. I have the impression the Maven devs regret > supporting it in the first place, but AFAIK, it's still supported. Thanks, Justin. The only reason I want to use LATEST in this case, is to have an automated launchpad build with all the latest checkins, for testing purposes. So that I don't have to update the bundle list XML when a bundle is released in a new version. In this case it seems LATEST makes sense - or are there other ways to accomplish what I want? > Can you post the maven-metadata.xml for this artifact from you repo manager > to a pastebin? Here: http://pastebin.com/uNpJMXQM I am using Maven 2.2.1 on my Mac OS 10.6 system, if that makes a difference. Any help appreciated, although I suspect it is more a Maven question than a Sling Launchpad question. -- 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!
