I was able to replicate with 3.0.2.
While it's old, it's not THAT old (2011) - so it would be reasonable that other could also still be using 3.0.2. The very quick solution would be a <prerequisites><maven>3.0.5. The problem with 3.0.2 is when you build a multi-module project and the extension is activated further in. I believe this Maven bug was: https://jira.codehaus.org/browse/MNG-4973 which was fixed in 3.0.3. I found a workaround - moving <extensions> declarations into <plugins> in jena-parent instead of <pluginManagement>. This should not affect the other modules in Jena unless they also try to use <packaging>bundle</packaging> (in which case they intend to use the bundle plugin :-)). Workaround: https://github.com/apache/jena/pull/32 Can you confirm that also works for your system? On 25 February 2015 at 12:32, Rob Vesse <[email protected]> wrote: > 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 > > > > -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
