<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Thomas,<div><br></div><div>First of all, if you want to use JBT, always install it in the Eclipse Java EE bundle. For SVN, use the 'Add Software' wizard and select the Subversion plugin from the Indigo update site (you'll find it in the category 'Collaboration'). If you do plugin development it might also be handy to install the Eclipse SDKs.<br><div><br></div><div>In any case your arguments and comments kind of support my earlier point. It is way more handy to install a pre made bundle of Eclipse plugins (such as the Java EE bundle and/or JBT) than to have to deal with all the individual Eclipse plugins. Even though you seem to have problems with the Eclipse way of managing plugins, I believe their system is not that bad if you stick to the 'blessed' bundles. So transposing this to Forge, it would be good to have our very own bundle(s) of 'blessed plugins' that can be installed as a batch in any runtime. This implies that there should be integration tests that test the installation and working of these bundles with their compatible runtime(s) as well as a mechanism to isolate different versions of the Forge plugin bundles if there is more than one version installed. There is already a 'pluginDir' option available that indicates that Forge needs to load plugins from and install them in the specified folder. This mechanism was created as a (partial) solution for the above problem but maybe it needs to become the default?</div><div><br></div><div>Cheers,</div><div>Koen</div><div><br></div><div>But first of all, if you want to use JBT, always install it in the Java<br><div><div>Op 31-mei-2012, om 08:22 heeft Thomas Frühbeck het volgende geschreven:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
Lincoln,<br>
are you one of those lucky guys who don't have to hassle regularly
with incompatible plugins in Eclipse? <br>
Just a hint: <br>
- I tried to install JBoss Tools 32bit into classic Eclipse
32bit on Win7 - it failed in the middle of installing ???<br>
- 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 <br>
- 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 ???<br>
<br>
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.<br>
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.)<br>
<br>
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. <br>
So I think one core features is a stable, manageable plugin life
cycle.<br>
<br>
Thomas<br>
<br>
Am 31.05.2012 07:40, schrieb Lincoln Baxter, III:
<blockquote cite="mid:CAEp_U4GdAKu2_yGRN+Tm5GQSDZPO3Nq-83QSMG7Rdyay8eDHSg@mail.gmail.com" type="cite">
<div class="gmail_quote">On Wed, May 30, 2012 at 6:18 PM, Burr
Sutter <span dir="ltr"><<a moz-do-not-send="true" href="mailto:bsutter@redhat.com" target="_blank">bsutter@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Well said Thomas - I am a great "dumb user" and plug-in
dependencies drive me nuts.<br>
</blockquote>
<div><br>
What do you mean by plug-in dependencies? What drives you
nuts?<br>
</div>
<br>
</div>
</blockquote>
<br>
</div>
_______________________________________________<br>forge-dev mailing list<br><a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/forge-dev<br></blockquote></div><br></div></div></body></html>