Skip to content

Conversation

@guw
Copy link

@guw guw commented Sep 14, 2023

Noticed those are missing in Maven Central. Can they be added please?

@a-langer
Copy link
Owner

Hi,

The console installer is intended mainly for automation via CI\CD, so builds are performed only for popular server architectures. If you need to run the installer on another platform, this can always be done via the command line, see wiki.eclipse.org:

# set path to eclipse folder. If the same folder as this script, use the default; otherwise, use /path/to/eclipse/
eclipsehome=`dirname $BASH_SOURCE`;

# get path to equinox jar inside $eclipsehome folder
cp=$(find $eclipsehome -name "org.eclipse.equinox.launcher_*.jar" | sort | tail -1);

# start Eclipse w/ java
java -cp $cp org.eclipse.equinox.launcher.Main  -application org.eclipse.oomph.console.application ...

Each installer weighs approximately 70 MB, and differs only in a certain number of native libraries. I would not like to fill Maven Central with almost identical artifacts, and besides, this complicates the deployment procedure.

In my opinion, it would be great to put together one multi-architecture installer that would contain native libraries for all architectures (for example, in different directories), but Eclipse Tycho cannot do this.

@a-langer
Copy link
Owner

Making console mode the default application 94a4eb4, in my opinion, would not be correct. In this case, we will lose the ability to run the installer in GUI mode (double-clicking on the executable file will not lead to the expected result), which complicates the procedure for debugging various Eclipse setup models. First of all, this should be a standard installer, and the no-interface mode can be activated from the command line and is intended for more advanced users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants