Firstly, be aware, if you're not already, that a plugin for JSPC compilation already exists; http://mojo.codehaus.org/jspc/index.html / http://mojo.codehaus.org/jspc/jspc-maven-plugin/usage.html
The current release, 2.0-alpha-3, despite the alpha label is stable and runs fine; it works with Tomcat 5 and Tomcat 6. The trunk also works with Tomcat 7, but isn't packaged up formally yet. There's also a ticket open for this plugin on M2E integration - http://jira.codehaus.org/browse/MJSPC-56 - that has links to the relevant page, namely http://wiki.eclipse.org/M2E_compatible_maven_plugins However, I find it just as easy to simply disable the JSPC compilation when running under M2E; it also aids with debugging. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=356311 for details of how this works for the afore mentioned plugin - you may find it easier to simply use this technique. either explicitly with another profile, or by detecting the presence of M2E within your plugin. HTH, Greg On 6 May 2013 17:41, Eric Dalquist <[email protected]> wrote: > I'm working on an update JSP compilation plugin and wondering how best > to make sure it plays nice with m2e. The plugin takes the JSP files and > generates java code, compiles that java code into class files, copies > those into the output directory and then modifies the web.xml file. > > The plugin binds to process-classes to do all of the > compilation/generation. > > Are there things I should/should not do to get this plugin to nicely > integrate into m2e? > > Thanks, > -Eric > > > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > >
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
