“For quick setup, zipped eclipse installations are available with the plugin pre-installed: Windows, Linux, Mac.”

It is not immediately evident to the casual browser that ‘Windows’ points to a zip file of Eclipse for Windows.

Submitted by Eelco Visser on 15 February 2010 at 17:32

On 15 February 2010 at 18:09 Danny Groenewegen commented:

fixed: http://webdsl.org/singlepage/WebDSLplugin

On 16 February 2010 at 09:43 Lennart Kats commented:

I’m not sure if it’s a good idea to actively promote these zip files. We need to reconsider what problem it is that they address. For the lab assignments they are great: students can download the zip and can create a temporary Eclipse installation on the fast C: drive with little hassle. For others, I’m not so sure if this is the best model. The Eclipse plugin manager is pretty bad, and this is a decent backup approach, but I think it should only be promoted as such.

Note that one problem that seems to have arised because of this way of distributing the plugin is WebDSL/28.

On 16 February 2010 at 09:49 Eelco Visser commented:

I agree that an update sites is preferable. The point was that if the zips are mentioned, it should be clear; the zips were linked with in one sentence with anchors ‘Windows’ from which it was not clear they were download links, nor how to use them.

On 24 February 2010 at 15:10 Danny Groenewegen commented:

So, should we just drop these pre-installed Eclipse zips? Right now, they are too much work to maintain anyway, since we have no automated way to build them.

On 24 February 2010 at 15:40 Lennart Kats commented:

Well right now they are still useful for the course: makes it easy for students to install a preconfigured Eclipse on the local hard drive.

On 4 May 2010 at 16:15 Nathan Bruning commented:

Maybe some Nix-expert can turn the script below in a hydra-build job. This would provide automatic zips and integration tests for Eclipse/Stratego/Spoofax/WebDSL/WebDSL editor.

The script unpacks an Eclipse tar and uses p2 to install the WebDSL plugin from some source location (can either be an update site or a local location). You can use both Eclipse-classic and Eclipse-EE, but the former requires downloading and installing WTP from Internet, which should be automatic but time consuming.


# emf is needed by org.eclipse.jst.ws.axis.creation.ui, org.eclipse.jst.ws.consumption

# ,${WTP_SITE}

# ECLIPSE_TAR=eclipse-SDK-3.5.2-linux-gtk-x86_64.tar.gz

echo "Copying eclipse..."

rm -rf eclipse
tar xzf $ECLIPSE_TAR
cd eclipse
echo "-server" >> eclipse.ini
echo "-Xss8m" >> eclipse.ini
mkdir -p configuration/.settings
# Copy predefined settings (workspace location)
cp ../org.eclipse.ui.ide.prefs configuration/.settings

echo "Installing Editor..."

java -jar plugins/org.eclipse.equinox.launcher_*.jar  \
   -application org.eclipse.equinox.p2.director \
   -metadataRepository ${ALL_SITES} \
   -artifactRepository ${ALL_SITES} \
   -installIU webdsl.editor.feature.feature.group \

On 4 May 2010 at 16:31 Lennart Kats commented:

Testing is good (maybe something for another issue). But right now the zips don’t work on older MacOSX systems and don’t work on 64-bit Linux (and that’s just the systems I know about). If we distribute zips it should be really clear what is supported and what is not. Ideally, everything should be supported.

On 4 July 2014 at 14:47 Danny Groenewegen closed this issue.

Log in to post comments