Having a single Eclipse installation, where simultaneous sessions are started up with different JDK...












0















Giving STS as an example.



I wish to have only one single installation of Eclipse STS 3.9.7. Normally I run more than one session of Eclipse/STS. I need to have




  • a couple sessions started on JDK 8

  • a session on JDK 10

  • another session on JDK 11


I also have an Eclipse 2018-12 installation. I wish to have only one such installation, from which I wish to start




  • a session in JDK 9

  • another session in OpenJDK 10


The only way I know how to specify the JDK is by specifying it on the ini config file. Perhaps there is another way. Therefore, currently I have multiple replicated copies of Eclipse/STS installations, each specified to start up from a different JDK.



Having proliferation of Eclipse/STS installations of the same version is very undesirable and confusing. Especially when I need to install or update modules from the Marketplace across all of them.



Is there a better way than having multiple replicated installations, in order to variously specify the JDK/bin/javaw paths to start up each of my sessions?










share|improve this question


















  • 3





    Why do you really care which version of Java is running Eclipse itself? You care about which version of Java is used by your projects, but that's defined by the project and/or workspace.

    – Andreas
    Jan 1 at 21:49











  • Running multiple sessions of the same Eclipse installation is a bad idea, since Eclipse caches files in the installation folder, and that'll be all messed up if you run multiple sessions. Use one session per installation, and learn to live with it.

    – Andreas
    Jan 1 at 21:51











  • "Use one session per installation, and learn to live with it" Are you sure you know how Eclipse works? A programmer who has only one Eclipse session?

    – Blessed Geek
    Jan 2 at 7:56






  • 1





    You can use the --launcher.ini xxx command line option to specify a different config.ini file.

    – greg-449
    Jan 2 at 7:59











  • I wonder why in this scenario multiple sessions are necessary: with a JDK 11 via the --release option as JDK 8 gives you compiler errors in both cases: if using stuff added after Java 8 and if using stuff removed in Java 9, 10 and 11.

    – howlger
    Jan 2 at 9:05


















0















Giving STS as an example.



I wish to have only one single installation of Eclipse STS 3.9.7. Normally I run more than one session of Eclipse/STS. I need to have




  • a couple sessions started on JDK 8

  • a session on JDK 10

  • another session on JDK 11


I also have an Eclipse 2018-12 installation. I wish to have only one such installation, from which I wish to start




  • a session in JDK 9

  • another session in OpenJDK 10


The only way I know how to specify the JDK is by specifying it on the ini config file. Perhaps there is another way. Therefore, currently I have multiple replicated copies of Eclipse/STS installations, each specified to start up from a different JDK.



Having proliferation of Eclipse/STS installations of the same version is very undesirable and confusing. Especially when I need to install or update modules from the Marketplace across all of them.



Is there a better way than having multiple replicated installations, in order to variously specify the JDK/bin/javaw paths to start up each of my sessions?










share|improve this question


















  • 3





    Why do you really care which version of Java is running Eclipse itself? You care about which version of Java is used by your projects, but that's defined by the project and/or workspace.

    – Andreas
    Jan 1 at 21:49











  • Running multiple sessions of the same Eclipse installation is a bad idea, since Eclipse caches files in the installation folder, and that'll be all messed up if you run multiple sessions. Use one session per installation, and learn to live with it.

    – Andreas
    Jan 1 at 21:51











  • "Use one session per installation, and learn to live with it" Are you sure you know how Eclipse works? A programmer who has only one Eclipse session?

    – Blessed Geek
    Jan 2 at 7:56






  • 1





    You can use the --launcher.ini xxx command line option to specify a different config.ini file.

    – greg-449
    Jan 2 at 7:59











  • I wonder why in this scenario multiple sessions are necessary: with a JDK 11 via the --release option as JDK 8 gives you compiler errors in both cases: if using stuff added after Java 8 and if using stuff removed in Java 9, 10 and 11.

    – howlger
    Jan 2 at 9:05
















0












0








0








Giving STS as an example.



I wish to have only one single installation of Eclipse STS 3.9.7. Normally I run more than one session of Eclipse/STS. I need to have




  • a couple sessions started on JDK 8

  • a session on JDK 10

  • another session on JDK 11


I also have an Eclipse 2018-12 installation. I wish to have only one such installation, from which I wish to start




  • a session in JDK 9

  • another session in OpenJDK 10


The only way I know how to specify the JDK is by specifying it on the ini config file. Perhaps there is another way. Therefore, currently I have multiple replicated copies of Eclipse/STS installations, each specified to start up from a different JDK.



Having proliferation of Eclipse/STS installations of the same version is very undesirable and confusing. Especially when I need to install or update modules from the Marketplace across all of them.



Is there a better way than having multiple replicated installations, in order to variously specify the JDK/bin/javaw paths to start up each of my sessions?










share|improve this question














Giving STS as an example.



I wish to have only one single installation of Eclipse STS 3.9.7. Normally I run more than one session of Eclipse/STS. I need to have




  • a couple sessions started on JDK 8

  • a session on JDK 10

  • another session on JDK 11


I also have an Eclipse 2018-12 installation. I wish to have only one such installation, from which I wish to start




  • a session in JDK 9

  • another session in OpenJDK 10


The only way I know how to specify the JDK is by specifying it on the ini config file. Perhaps there is another way. Therefore, currently I have multiple replicated copies of Eclipse/STS installations, each specified to start up from a different JDK.



Having proliferation of Eclipse/STS installations of the same version is very undesirable and confusing. Especially when I need to install or update modules from the Marketplace across all of them.



Is there a better way than having multiple replicated installations, in order to variously specify the JDK/bin/javaw paths to start up each of my sessions?







java eclipse spring-tool-suite






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 1 at 21:40









Blessed GeekBlessed Geek

11.4k1784151




11.4k1784151








  • 3





    Why do you really care which version of Java is running Eclipse itself? You care about which version of Java is used by your projects, but that's defined by the project and/or workspace.

    – Andreas
    Jan 1 at 21:49











  • Running multiple sessions of the same Eclipse installation is a bad idea, since Eclipse caches files in the installation folder, and that'll be all messed up if you run multiple sessions. Use one session per installation, and learn to live with it.

    – Andreas
    Jan 1 at 21:51











  • "Use one session per installation, and learn to live with it" Are you sure you know how Eclipse works? A programmer who has only one Eclipse session?

    – Blessed Geek
    Jan 2 at 7:56






  • 1





    You can use the --launcher.ini xxx command line option to specify a different config.ini file.

    – greg-449
    Jan 2 at 7:59











  • I wonder why in this scenario multiple sessions are necessary: with a JDK 11 via the --release option as JDK 8 gives you compiler errors in both cases: if using stuff added after Java 8 and if using stuff removed in Java 9, 10 and 11.

    – howlger
    Jan 2 at 9:05
















  • 3





    Why do you really care which version of Java is running Eclipse itself? You care about which version of Java is used by your projects, but that's defined by the project and/or workspace.

    – Andreas
    Jan 1 at 21:49











  • Running multiple sessions of the same Eclipse installation is a bad idea, since Eclipse caches files in the installation folder, and that'll be all messed up if you run multiple sessions. Use one session per installation, and learn to live with it.

    – Andreas
    Jan 1 at 21:51











  • "Use one session per installation, and learn to live with it" Are you sure you know how Eclipse works? A programmer who has only one Eclipse session?

    – Blessed Geek
    Jan 2 at 7:56






  • 1





    You can use the --launcher.ini xxx command line option to specify a different config.ini file.

    – greg-449
    Jan 2 at 7:59











  • I wonder why in this scenario multiple sessions are necessary: with a JDK 11 via the --release option as JDK 8 gives you compiler errors in both cases: if using stuff added after Java 8 and if using stuff removed in Java 9, 10 and 11.

    – howlger
    Jan 2 at 9:05










3




3





Why do you really care which version of Java is running Eclipse itself? You care about which version of Java is used by your projects, but that's defined by the project and/or workspace.

– Andreas
Jan 1 at 21:49





Why do you really care which version of Java is running Eclipse itself? You care about which version of Java is used by your projects, but that's defined by the project and/or workspace.

– Andreas
Jan 1 at 21:49













Running multiple sessions of the same Eclipse installation is a bad idea, since Eclipse caches files in the installation folder, and that'll be all messed up if you run multiple sessions. Use one session per installation, and learn to live with it.

– Andreas
Jan 1 at 21:51





Running multiple sessions of the same Eclipse installation is a bad idea, since Eclipse caches files in the installation folder, and that'll be all messed up if you run multiple sessions. Use one session per installation, and learn to live with it.

– Andreas
Jan 1 at 21:51













"Use one session per installation, and learn to live with it" Are you sure you know how Eclipse works? A programmer who has only one Eclipse session?

– Blessed Geek
Jan 2 at 7:56





"Use one session per installation, and learn to live with it" Are you sure you know how Eclipse works? A programmer who has only one Eclipse session?

– Blessed Geek
Jan 2 at 7:56




1




1





You can use the --launcher.ini xxx command line option to specify a different config.ini file.

– greg-449
Jan 2 at 7:59





You can use the --launcher.ini xxx command line option to specify a different config.ini file.

– greg-449
Jan 2 at 7:59













I wonder why in this scenario multiple sessions are necessary: with a JDK 11 via the --release option as JDK 8 gives you compiler errors in both cases: if using stuff added after Java 8 and if using stuff removed in Java 9, 10 and 11.

– howlger
Jan 2 at 9:05







I wonder why in this scenario multiple sessions are necessary: with a JDK 11 via the --release option as JDK 8 gives you compiler errors in both cases: if using stuff added after Java 8 and if using stuff removed in Java 9, 10 and 11.

– howlger
Jan 2 at 9:05














2 Answers
2






active

oldest

votes


















1














You can use the --launcher.ini <path> command line option to specify a different 'config.ini' file to use when starting Eclipse.






share|improve this answer
























  • The ini has to be within the Eclipse installation, otherwise Eclipse will croak "shared lib not found".

    – Blessed Geek
    Jan 2 at 8:30



















1














As an alternative to --launcher.ini <path> already mentioned by greg-449, there is a trick that works without any command line argument:



Copy the executable (eclipse.exe on Windows, eclipse on macOS and Linux) and the eclipse.ini files. When you execute the renamed executable file, the correspondingly renamed .ini file instead of eclipse.ini is used.






share|improve this answer
























  • I made a hard link.

    – Blessed Geek
    Jan 4 at 7:55











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53999160%2fhaving-a-single-eclipse-installation-where-simultaneous-sessions-are-started-up%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














You can use the --launcher.ini <path> command line option to specify a different 'config.ini' file to use when starting Eclipse.






share|improve this answer
























  • The ini has to be within the Eclipse installation, otherwise Eclipse will croak "shared lib not found".

    – Blessed Geek
    Jan 2 at 8:30
















1














You can use the --launcher.ini <path> command line option to specify a different 'config.ini' file to use when starting Eclipse.






share|improve this answer
























  • The ini has to be within the Eclipse installation, otherwise Eclipse will croak "shared lib not found".

    – Blessed Geek
    Jan 2 at 8:30














1












1








1







You can use the --launcher.ini <path> command line option to specify a different 'config.ini' file to use when starting Eclipse.






share|improve this answer













You can use the --launcher.ini <path> command line option to specify a different 'config.ini' file to use when starting Eclipse.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 2 at 8:29









greg-449greg-449

89.7k166399




89.7k166399













  • The ini has to be within the Eclipse installation, otherwise Eclipse will croak "shared lib not found".

    – Blessed Geek
    Jan 2 at 8:30



















  • The ini has to be within the Eclipse installation, otherwise Eclipse will croak "shared lib not found".

    – Blessed Geek
    Jan 2 at 8:30

















The ini has to be within the Eclipse installation, otherwise Eclipse will croak "shared lib not found".

– Blessed Geek
Jan 2 at 8:30





The ini has to be within the Eclipse installation, otherwise Eclipse will croak "shared lib not found".

– Blessed Geek
Jan 2 at 8:30













1














As an alternative to --launcher.ini <path> already mentioned by greg-449, there is a trick that works without any command line argument:



Copy the executable (eclipse.exe on Windows, eclipse on macOS and Linux) and the eclipse.ini files. When you execute the renamed executable file, the correspondingly renamed .ini file instead of eclipse.ini is used.






share|improve this answer
























  • I made a hard link.

    – Blessed Geek
    Jan 4 at 7:55
















1














As an alternative to --launcher.ini <path> already mentioned by greg-449, there is a trick that works without any command line argument:



Copy the executable (eclipse.exe on Windows, eclipse on macOS and Linux) and the eclipse.ini files. When you execute the renamed executable file, the correspondingly renamed .ini file instead of eclipse.ini is used.






share|improve this answer
























  • I made a hard link.

    – Blessed Geek
    Jan 4 at 7:55














1












1








1







As an alternative to --launcher.ini <path> already mentioned by greg-449, there is a trick that works without any command line argument:



Copy the executable (eclipse.exe on Windows, eclipse on macOS and Linux) and the eclipse.ini files. When you execute the renamed executable file, the correspondingly renamed .ini file instead of eclipse.ini is used.






share|improve this answer













As an alternative to --launcher.ini <path> already mentioned by greg-449, there is a trick that works without any command line argument:



Copy the executable (eclipse.exe on Windows, eclipse on macOS and Linux) and the eclipse.ini files. When you execute the renamed executable file, the correspondingly renamed .ini file instead of eclipse.ini is used.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 2 at 8:41









howlgerhowlger

11.3k51839




11.3k51839













  • I made a hard link.

    – Blessed Geek
    Jan 4 at 7:55



















  • I made a hard link.

    – Blessed Geek
    Jan 4 at 7:55

















I made a hard link.

– Blessed Geek
Jan 4 at 7:55





I made a hard link.

– Blessed Geek
Jan 4 at 7:55


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53999160%2fhaving-a-single-eclipse-installation-where-simultaneous-sessions-are-started-up%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Angular Downloading a file using contenturl with Basic Authentication

Olmecas

Can't read property showImagePicker of undefined in react native iOS