Since JBT 4.3.0.Final is slated for after Mars SR1, this seems reasonable.
You don't technically need to have the same IU names to allow a seamless
upgrade from o.j.t.whatever to o.eclipse.wtp.whatever.
We've seen multiple instances where a JBoss project moved to Eclipse,
and we were able to support the IU rename using a p2.inf instruction.
Here's what we did to rename from com.jboss.jbds to com.jboss.devstudio:
We've done similar with m2e-wtp, too.
But of course it's simpler if we just build the plugin using the future
o.e.wtp name, and a lower version.
On 05/19/2015 04:58 PM, Rob Stryker wrote:
wtp-dev mailing list seems to indicate its a bit too late to get such a
contribution into Mars. They did suggest it might be reasonable for SR1.
With that in mind, we should discuss how to go about getting this into
JBT for our Mars release, while still allowing it to be removed /
overridden by the eventual contribution to SR1.
As of now, it seems the thing most important to discuss is naming of the
plugin, to ensure that the name we use matches with the WTP one. The
idea seems to be that if we release this plugin as 0.9.0 in JBT, it can
be added to WTP for Mars SR1 with a higher version, thus replacing ours.
The issue at wtp can be discussed here:
@Nick: Any ideas on whether this plan makes sense?
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio