Abel,
Please don't confuse users. There is no need for WTP to look at
anything specific. The whole point of attributes is that they are plugin
agnostic. So, as long as WTP can recognize some attributes, other
plugins can manage them.
Anyways, I've suggested several times that anyone interested in WTP
integration should start putting together requirements on the project
wiki. I just created page for that, so please feel free to edit it. Let
me know if you have issues with permissions.
http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+WTP
regards,
Eugene
Abel Muiño wrote:
As far as I can tell, nothing has gone into trunk.
The patch MNGECLIPSE-105-wtp2.0.patch in MNGECLIPSE-105 adds support for
deploying dependencies to the web container, filtering the scopes.
I can't speak for MNGECLIPSE-107, but by the description of the solution, it
will do nothing useful (as WTP is not looking for m2eclipse specific
attributes).
Paul G wrote:
Can someone please tell me the situation regarding M2-eclipse and WTP
integration, the main details are in the following 2 jira issus.
http://jira.codehaus.org/browse/MNGECLIPSE-105
http://jira.codehaus.org/browse/MNGECLIPSE-105 and
http://jira.codehaus.org/browse/MNGECLIPSE-107
http://jira.codehaus.org/browse/MNGECLIPSE-107
What is happening with this? What code has been integrated into the trunk,
what functionality can I expect if I build from the trunk? Will
integration with WTP 2.0 be included in the 0.11 release, when ever that
will be?
Cheers
Paul
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
