The "jdt" id doesn't exist, you must use "eclipse". See http://maven.apache.org/plugins/maven-compiler-plugin/non-javac-compilers.html
On Sun, Jan 22, 2012 at 4:35 PM, Stephan Herrmann <[email protected]>wrote: > Thanks, Fred, much appreciated. > > Just a quick question: > Previous examples I saw used to specify a compilerId of "jdt". > What's the difference when saying "eclipse" instead of "jdt"? > > thanks, > Stephan > > On Sunday, January 22, 2012 04:15:06 PM Fred Bricon wrote: > > Hi, > > > > FWIW, I've created a plugin to allow maven-compiler-plugin using > > compilerId=eclipse to be used transparently with m2e (by > > using org.eclipse.m2e.jdt.javaConfigurator). > > Source code is available from > > https://github.com/fbricon/m2e-jdt-compilerfor now (I may transfer it > > to the jbosstools organization later this week), > > but most importantly, you can install ci builds from this p2 update site > : > > > http://download.jboss.org/jbosstools/builds/staging/m2e-jdt-compiler/all/repo/ > > > > Using this eclipse plugin, no new lifecycle mapping is necessary in your > > pom.xml. > > > > HIH > > > > Fred Bricon > > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > -- "Have you tried turning it off and on again" - The IT Crowd
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
