[jbosstools-dev] Ideas to make m2eclipse-wtp -> m2e-wtp migration painless?

Fred Bricon fbricon at gmail.com
Mon Jul 9 08:34:34 EDT 2012


Hi all,

I'm currently banging my head on the m2eclipse-wtp -> m2e-wtp migration, so
if anyone as any good ideas, I'm open to suggestions.

Here's what we have :
- m2e-wtp (@eclipse) uses a new namespace for eclipse plugins/features :
org.eclipse.m2e.wtp instead of org.maven.ide.wtp
- m2e-wtp keeps the m2eclipse-wtp configurator identifiers to maintain
backward compatibility with 3rd party plugins (JBoss Tools ecosystem,
Google Eclipse Plugin ...)
- m2e-wtp installation doesn't disable m2eclipse-wtp plugins since the
namespace changed.
- installing m2e-wtp over m2eclipse-wtp is bad (as "crossing the streams"
bad) since m2e-core now finds duplicate configurators which produces errors.
- I created (locally) an m2eclipse-wtp 0.15.999 empty feature that
requires m2e-wtp 0.16.0. m2e-wtp is correctly installed but I'm still
seeing the duplicate configurators as previous m2eclipse-wtp 0.15.2 plugins
are still active.

Ideally m2e-wtp would disable m2eclipse-wtp when installed, but I'm afraid
it seems impossible (yeah I suck at eclipse/OSGi stuff).
So that means the only way to install m2e-wtp for existing m2eclipse-wtp
users will be to either start from a pristine eclipse installation or
uninstall m2eclipse-wtp beforehand, breaking the update process for
products already embedding m2eclipse-wtp.

Hopefully I'm missing something. Sooo, any ideas?

Regards,

Fred Bricon
-- 
"Have you tried turning it off and on again" - The IT Crowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20120709/32a67835/attachment.html 


More information about the jbosstools-dev mailing list