Hi all,

we have a custom packaging type for war artefacts that executes a few
additional goals specific to our needs
extending the default war lifecycle. The custom packaging works create on
the commandline but importing
these projects into the eclipse ide leaves us with a project that is not
deployable to an wtp target (tomcat).

What is the easiest way to tell m2e, m2e-wtp to treat this project like an
"normal" war project?

As far as I understand m2e-wtp only executes the wtp special configuration
for packaging types mentioned here:
http://git.eclipse.org/c/m2e-wtp/org.eclipse.m2e.wtp.git/tree/org.eclipse.m2e.wtp/src/org/eclipse/m2e/wtp/ProjectConfiguratorDelegateFactory.java

The WebProjectConfiguratorDelegate that actually carries out the
configuration work is also only package visible.
In the past I wrote plugin that used reflection to make the plugins
internal code accessible and delegate to it
but with our recent upgrade to Kepler I revisited the code and it just felt
so wrong..

Generally I would like to avoid implementing an eclipse plugin in order to
not tie our "platform" to an eclipse
release.


Best regards,

Nils
_______________________________________________
m2e-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to