Re: [forge-dev] How should plugins keep up with api updates

Lincoln, are you one of those lucky guys who don't have to hassle regularly with incompatible plugins in Eclipse? Just a hint: - I tried to install JBoss Tools 32bit into classic Eclipse 32bit on Win7 - it failed in the middle of installing ??? - SVN: there are two prominent plugins, incompatible, one looking half way like the other but handling is very different in the hard cases, PITA from start to end, I see myself reverting regularly to the command line - for some time recently I couldn't update my m2e plugin because it carried a dependency to a something in version 1.1 which was not released yet ??? Have a look at the different flavors Eclipse IDE bundles - to me the main reason for those is: plug-in (inter-) dependencies and plug-in management. I don't want to complain, but to me these are the everyday problems I face _after_ I told my boss that the fix xxx will only take an hour :-/ (The fix itself may take 5 minutes, the rest of the day it will take to get the infrastructure of the project up and running again.) And then we are programmers open for the newest, latest, greatest. And of course any author of a plugin would want his customers to pick up the new functionality ASAP. So I think one core features is a stable, manageable plugin life cycle. Thomas Am 31.05.2012 07:40, schrieb Lincoln Baxter, III: