Pierre-Arnaud Marcelot schrieb: > Hi Felix, > > These are great ideas. > > I think we can do both. > > 1°/ Add a nightly build update site on the oxylos machine where we > deploy the latest update site (as you said). People will be able to > install the snapshot version using the standard eclipse way. > > 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.
> > 2°/ We can also provide the update site as an archive download (zip) > that users can use to manually install in their Eclipse folder (the > JBoss solution). > > Regards, > Pierre-Arnaud > > > On Thu, Sep 11, 2008 at 9:48 AM, Felix Knecht <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Felix Knecht schrieb: > > Hi all > > > > For the dist we are ATM deploying a snapshot dist. > > Do you think it's worth to do the same for the plugin update site to > > have something like > > > > > > http://vm094.oxylos.org/mirror-maven2/org/apache/directory/studio/ApacheDirectoryStudio/update/dev > > (similar to http://directory.apache.org/studio/update/1.x/) > > > > where we deploy the latest update site for the eclipse plugin? > > If so the next question would be 'How does eclipse recognize > that the > > update site has changed?'. I don't know if this > > works by just deploying the updatesite-x-SNAPSHOT.tar.gz to the > URL above. > > Another possibility could be deploy a nightly snapshot of the plugin > which can be linked into eclipse like the jbosstools [1] do for their > nightly snapshots. > > [1] http://wiki.jboss.org/wiki/InstallingJBossToolsNightlyBuilds > > > > WDOT? > > > > Felix > > > >
