On 12/12/2007, Elvy <[EMAIL PROTECTED]> wrote: > > > I removed the apache snapshot rep from my repositories, added OSP4J as you > said, and all my non OSGi project are doing fine (as far as surefire is > concerned). However, I now have issues with maven-bundle-plugin... > > > __________________________________________________________________________________________ > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > Missing: > ---------- > 1) org.apache.maven.shared:maven-dependency-tree:jar:1.1-SNAPSHOT > > ... > > Path to dependency: > 1) > org.apache.felix:maven-bundle-plugin:maven-plugin:1.1.0-SNAPSHOT > 2) org.apache.maven.shared:maven-dependency-tree:jar:1.1-SNAPSHOT > > 2) org.apache.maven.shared:maven-osgi:jar:0.2.0-SNAPSHOT > > ... > > Path to dependency: > 1) > org.apache.felix:maven-bundle-plugin:maven-plugin:1.1.0-SNAPSHOT > 2) org.apache.maven.shared:maven-osgi:jar:0.2.0-SNAPSHOT > > ---------- > 2 required artifacts are missing. > > for artifact: > org.apache.felix:maven-bundle-plugin:maven-plugin:1.1.0-SNAPSHOT > > __________________________________________________________________________________________ > > this is all out of my control I guess... sniff
very peculiar since several people (including Spring-DM) have been happily using the bundle-plugin from the OPS4J plugin repository without this error - to see an example working Maven project, just look at the Pax-Construct examples have you tried clearing out your .m2/repository/org/apache/felix/maven-bundle-plugin repo folder ? it may be that Maven has some bad metadata somewhere - when I start from a clean repository Maven detects the extra repos in the Felix parent pom (referenced from the bundle-plugin pom) and downloads the shared SNAPSHOT components from 'apache.snapshots' other things to check: do you use any repo definitions for the apache snapshot repo that might change the update settings (ie. do you set <updatePolicy>never</updatePolicy> anywhere?) also you can try using "mvn -U ..." to force Maven to check snapshots on remote repositories When is a final 1.1.0 version of maven-bundle-plugin gonna be released? we're (still) waiting for the Maven team to release those snapshot components - but as it looks like this won't happen before 2008, I'm going to revert to the earlier versions and do a release (possibly next week) - reverting these components only affects people using the bundleall goal once it's released I'll reapply the snapshot components to the new bundle-plugin snapshot Stuart McCulloch wrote: > > > > On 12/12/2007, Stuart McCulloch <[EMAIL PROTECTED]> wrote: > >> > >> On 11/12/2007, Elvy <[EMAIL PROTECTED]> wrote: > >> > > >> > > >> > I indeed have the apache snapshot repo listed as a plugin repo. > >> > > >> > Is there a way to explicitly tell maven to use the latest > non-snapshot > >> > surefire version? > >> > >> > > FYI, you can set RELEASE as the version to get the latest release (ie. > > non-snapshot) > > > > yes, just put something like: > >> > >> <plugin> > >> <groupId>org.apache.maven.plugins</groupId> > >> <artifactId>maven-surefire-plugin</artifactId> > >> <version>2.3</version> > >> </plugin> > >> > >> in the <build><plugins> or <build><pluginManagement><plugins> part of > the > >> POM > >> > >> you can also use the enforcer plugin to lock down versions: > >> > >> > >> > http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requirePluginVersions.html > >> > >> (this plugin also lets you lock down other settings to ensure > >> reproducible > >> builds) > >> > >> > correct, this is an issue with the maven-surefire-plugin - for some > >> > reason > >> > > you seem to be picking up a snapshot of this plugin, are you > >> > referencing > >> > > this in your POM, or do you have the apache snapshot repository > >> listed > >> > as > >> > > a plugin repository? > >> > > > >> > > ( the apache snapshot repo is > >> > > http://people.apache.org/repo/m2-snapshot-repository ) > >> > > > >> > > adding the apache snapshot repository as a plugin repository is not > >> > > recommended, as it ends up pulling in snapshots of maven plugins - > if > >> > you > >> > > just want the 1.1.0-SNAPSHOT version of the bundle plugin you can > use > >> > the > >> > > OPS4J snapshot repository: > >> > > > >> > > <pluginRepository> > >> > > <id>ops4j-snapshots</id> > >> > > <url>http://repository.ops4j.org/mvn-snapshots</url> > >> > > <releases> > >> > > <enabled>false</enabled> > >> > > </releases> > >> > > </pluginRepository> > >> > > > >> > > you could try using "mvn help:effective-pom" to show the combined > POM > >> > that > >> > > Maven sees after it's combined it with the parent POM, etc. - or > use > >> > "mvn > >> > > -X install" to trace where the surefire plugin snapshot is pulled > in > >> > > from... > >> > > > >> > > >> > ----- > >> > Tell me something you don't know! > >> > -- > >> > View this message in context: > >> > http://www.nabble.com/what-about-plexus-utils-1.4.9-SNAPSHOT--tp14273678p14276111.html > >> > > >> > Sent from the Apache Felix - Users mailing list archive at Nabble.com > . > >> > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > For additional commands, e-mail: [EMAIL PROTECTED] > >> > > >> > > >> > >> > >> -- > >> Cheers, Stuart > > > > > > > > > > -- > > Cheers, Stuart > > > > > > > ----- > Tell me something you don't know! > -- > View this message in context: > http://www.nabble.com/what-about-plexus-utils-1.4.9-SNAPSHOT--tp14273678p14294439.html > Sent from the Apache Felix - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
