| Summary: | [mojo] org.codehaus.mojo.jspc:jspc-maven-plugin support | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | gdt <greg.d.thomas> | ||||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||||
| Status: | CLOSED INVALID | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | igor | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
gdt
Created attachment 203762 [details]
Improved solution to the problem
I've attached what I think is a better solution to the problem;
The attached ZIP file has two profiles; one is activated outside of m2e, and pre-compiles the JSP pages and use the modified web.xml file in the WAR file.
by having two profiles
The other is activated when running with m2e; it has no settings, so uses the default of no-precompiled JSP pages and the original web.xml file.
This works well; when running in Eclipse, the source JSP files are used, and when packaged, the pre-compiled ones are used.
closing old/stale bugreports |