This is just one more of those Maven things... Before releasing Qi4j 1.0, I put in place the Maven Enforcer Plugin, which makes sure that every version of every plugin used is specified. So, now you are using an unversioned (LATEST) plugin.
Quick work around for you is to add the eclipse plugin and version in the <pluginsManagement> section of the poms. Then we will figure out what to do with the whole Maven headache (or not)... Cheers On Sun, Jan 31, 2010 at 10:38 PM, Georg Ragaller <[email protected]> wrote: > When building from source, I used to work with > the eclipse:clean and eclipse:eclipse targets to generate > fresh eclipse project and classpath settings after a pull. > This doesn't work any longer out of the box with the latest source. > I get something like: > > <snip> > H:\java\qi4j\qi4j-core>mvn eclipse:eclipse > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Qi4j Build tools > [INFO] Qi4j Core (Build POM) > [INFO] Qi4j Core - API > [INFO] Qi4j Core - SPI > [INFO] Qi4j Core - Bootstrap > [INFO] Qi4j Core - Test Support > [INFO] Qi4j Core - Runtime > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Qi4j Build tools > [INFO] task-segment: [eclipse:eclipse] > [INFO] > ------------------------------------------------------------------------ > [INFO] Preparing eclipse:eclipse > [INFO] No goals needed for project - skipping > [INFO] [eclipse:eclipse {execution: default-cli}] > [INFO] Using Eclipse Workspace: H:\java\qi4j > [INFO] Adding default classpath container: > org.eclipse.jdt.launching.JRE_CONTAINER > [INFO] Not writing settings - defaults suffice > [INFO] Wrote Eclipse project for "qi4j-buildtools" to > H:\java\qi4j\qi4j-core\build-tools. > [INFO] > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Qi4j Core (Build POM) > [INFO] task-segment: [eclipse:eclipse] > [INFO] > ------------------------------------------------------------------------ > [INFO] Preparing eclipse:eclipse > [INFO] [enforcer:enforce {execution: enforce-plugin-versions}] > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequirePluginVersions > failed with message: > Some plugins are missing valid versions:(LATEST RELEASE SNAPSHOT are not > allowed ) > org.apache.maven.plugins:maven-eclipse-plugin. The version currently in use > is 2.7 > Best Practice is to always define plugin versions! > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Some Enforcer rules have failed. Look above for specific messages > explaining why the rule failed. > [INFO] > ------------------------------------------------------------------------ > [INFO] For more information, run Maven with the -e switch > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 6 seconds > [INFO] Finished at: Sun Jan 31 15:24:32 CET 2010 > [INFO] Final Memory: 21M/50M > [INFO] > ------------------------------------------------------------------------ > </snip> > > Can anyone confirm the problem? > > I've worked around it by using > > mvn eclipse:eclipse -Denforcer.skip=true > > to skip the enforcer plugin settings, so it's not that a problem, but > perhaps the maven gurus out there can fix it sometime. > > Thanks, > Georg > > > > > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
