Re: [m2e-users] wb-resource naive question
m2e-wtp doesn't use /target/APPNAME. That folder is created during CLI builds, in the package phase.
In Eclipse w/ WTP, deployment is incremental and source folders are directly referenced for publishing. Typically :
- src/main/webapp will contain your web resources
- target/m2e-wtp/web-resources/ contain automatically generated web resources (and need to be referenced before src/main/webapp in the deployment assembly)
Now for overlays, if the referenced overlay is an archive, it'll be unzipped under target/m2e-wtp/overlays/<archivename>. Overlaid workspace projects are referenced with a custom handle in the
.settings/org.eclipse.wst.common.component. This settings allow overlay changes to be published on the fly.
Note that overlay support might vary depending on the server adapter you're using. I've been testing it with Tomcat and JBoss AS 7. For the moment Tomcat's "Serve modules without publishing" feature is not compatible with m2e-wtp's overlays, so you must use the stock settings which publish the modified resources to a staging area
On Tue, Jul 17, 2012 at 4:48 PM, l.penet@xxxxxxxx <l.penet@xxxxxxxx>
Another simple question from a new user.
I have a maven project using the war overlay mechanism. I am using :
* m2e 1.1.0
* Maven integration for WTP 0.16
Yet, I still have to manually modifiy the .settings/org.eclipse.wst.common.component
to add a line like :
<wb-resource deploy-path="/" source-path="/target/APPNAME"/>
Can you please tell me where I miss something ?
Sorry in advance, but I looked in archive and did not find a similar question.
| AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT.
m2e-users mailing list
"Have you tried turning it off and on again" - The IT Crowd