![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
2.0-alpha-2 |
|
Assignee:
|
Unassigned |
|
Created:
|
31/Jul/12 8:05 AM
|
|
Description:
|
(version is actually 2.0-alpha-3 - but that's not accepted)
Currently, if you attempt to use the JSPC plugin with m2e, you get an error message "Plugin execution not covered by lifecycle configuration". See the page at http://wiki.eclipse.org/M2E_plugin_execution_not_covered for the background to this.
There's an attachment at https://bugs.eclipse.org/bugs/show_bug.cgi?id=356311 which shows how to avoid the error; I simply have two profiles in my pom.xml; one pre-compiles the jsp and uses jspweb.xml when running outside of Eclipse, the other simply skips the pre-compilation altogether and uses the original web.xml when running inside Eclipse.
However, reading http://wiki.eclipse.org/M2E_compatible_maven_plugins suggests that there is a way to make the plugin compatible with m2e without all this pom.xml messiness.
It would be good to be able to support m2e properly in this manner.
|
|
Project:
|
Maven 2.x JSPC Plugin
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Greg Thomas
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
