Stian Turns out our build servers are using the veritably ancient mvn 3.0.2
Adding <extensions> directly makes no difference I'll see what can be done to upgrade Maven on our build servers and see if that resolves the issue. Rob On 24/02/2015 17:36, "Stian Soiland-Reyes" <[email protected]> wrote: >I tested with mvn 3.2.1, 3.0.5 and 2.2.1 without being able to reproduce. > >Did it work with the <extensions> added directly? Perhaps in older >Maven it's not >picked up from <pluginManagement> > > >On 24 February 2015 at 15:42, Rob Vesse <[email protected]> wrote: >> Stian >> >> When we try and build Jena on our internal build servers we see the >> following error: >> >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce (enforce) >>on >> project jena-osgi: >>org.apache.maven.plugins.enforcer.RequirePluginVersions >> failed with message: >> [ERROR] Cannot find lifecycle mapping for packaging: 'bundle'. >> [ERROR] -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with >>the -e >> switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, >>please >> read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> [ERROR] >> [ERROR] After correcting the problems, you can resume the build with the >> command >> [ERROR] mvn <goals> -rf :jena-osgi >> >> Any ideas how to resolve this? >> >> It may be we are missing a plugin on our end or this is something to do >>with >> having an old version of Maven on our build servers. We're not OSGI >>people >> so we are stumped by this currently and goggling hasn't yielded any >>useful >> ideas >> >> Rob >> >> > > > >-- >Stian Soiland-Reyes >Apache Taverna (incubating) >http://orcid.org/0000-0001-9842-9718
