you are right. I should have been more specific. M2e-wtp is actually causing the trouble in our scenario. Its been a while since I last visited our eclipse integration..
Our current approach is actually to delegate into m2e-wtp configuration code in the right places to treat our artifacts (project) as "normal" wtp war projects. In order to get the wtp integration working, we are running aÂ custom eclipse plugin that uses a reflection hack todo so. This works to a certain extend but there are other places within m2e-wtp that will prevent our
project from a proper configuration on project import.
So I am interested on the status on m2e-wtp 2.0 and the support for custom war packaging types .
Currently for us it basically boils down to two options:
* Drop support for our custom war packaging types
* Drop support for eclipse m2e-wtp
None of the them are really great, so I am wondering about any alternatives.