Ah yeah, I omitted to read the most important part of the JBoss documentation: Section "Better management of external plugins".
I like this solution. +1 for it. Pierre-Arnaud On Thu, Sep 11, 2008 at 10:54 AM, Felix Knecht <[EMAIL PROTECTED]> wrote: > Pierre-Arnaud Marcelot schrieb: > > Well, I was thinking we could tell our users they need to copy/paste > > the content of the 'plugins' and 'features' folders of the ZIP on the > > corresponding folders of their Eclipse installation. > > > > That's not a very difficult task, so I think they can do it easily. > Yes, that's easy. But you pollute your eclipse installation this way > with nightly snapshot you want to be able to change them easily. The way > it's done by jboss you have a link to a directory which is 'static'. The > directory itself can be deleted and/or updated (delete content and unzip > newer nightly snapshot) easier than removing the copied plugins/features > jars from an eclipse installation and recopy the newer ones. > Note that you'll be forced to delete the older jars all because you > never now if the are obsolete within a newer nightly release. > > That's way the solution using the link stuff should be proferred IMO. > > > > > Pierre-Arnaud > > > > On Thu, Sep 11, 2008 at 10:44 AM, Felix Knecht <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Pierre-Arnaud Marcelot schrieb: > > > Hi Felix, > > > > > > On Thu, Sep 11, 2008 at 10:33 AM, Felix Knecht > > <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > > > > > > > > > Unfortunately, Eclipse won't be able to find an update > > between two > > > > builds of this nightly update site (as the version number > > will stay > > > > the same). The solution would be to uninstall Studio's > > features and > > > > plugins before re-installing them with the update site. > > > IMO this is too complex for a 'normal' user. Thus I'd vote > > only for 2. > > > > > > > > > Yeah, but I don't think a "normal" user would try to use a nightly > > > version of Studio. ;) > > > > > > However, I think solution 2 is enough and as we already have the > zip > > > generated at each build. > > Nope. This zip must have another directory structure to make it > > work. It > > must look like > > > > eclipse > > \ plugins > > \ features > > > > Otherwise it won't work :-( > > > > > > > We just need to deploy it aside the other already available > > downloads. > > > > > > Pierre-Arnaud > > > > > >
