Launch of portable eclipse is not possible in multi user environment (development server shared by many developers via remote desktop with private installation of eclipse for each user in home directory) If I start via eclipse.exe in directory /app/eclipse providing the -vm option pointing to the correct java runtime all is fine, when starting via EclipsePortable.exe error "another instance of eclipse XXX is already running" prevents running eclipse. Is there an option in the launcher ini or any...
update to Eclipse 4.23
Dear Berny, Thank you very much for the eclipse portable 22, that I have just installed. Unfortunately it gives me the following error: incompatible JVM. It’s probably because I have installed the Java Runtime environment last found on the internet. But I have jPortable as well. I have added in eclipse.ini the path to be taken to get javaw.exe via jportable, but it doesn’t help. It still gives me the same error, therefore I cannot use eclipse portable. I would very much appreciate your help, thank...
update to Eclipse 4.22
update to Eclipse 4.21
add "Buy Me a Coffee" donation link
update to Eclipse 4.20
👍
Home
Home
Thank you, I have updated all previous major releases (4.6 to 4.19) to include the change.
remove eclipse.ini, update prefs
Troubleshooting
Installation
Install Features
Installation
update help.html
remove startscript, update to Eclipse 4.19
Maybe you will change [Launch] section in Launcher/EclipsePortable.ini: from this ProgramExecutable=StartScript\StartScript.bat to this ProgramExecutable=eclipse\eclipse.exe and add two Environment Variables to [Environment] section: JAVA_HOME=%PAL:PortableAppsDir%\CommonFiles\OpenJDK64 PATH=%JAVA_HOME%\bin;%PATH% Instead of running StartScript.bat to copy full Java directory to eclipse directory? :)
Maybe you will change [Launch] section in Launcher/EclipcePortable.ini: from this ProgramExecutable=StartScript\StartScript.bat to this ProgramExecutable=eclipse\eclipse.exe and add two Environment Variables to [Environment] section: JAVA_HOME=%PAL:PortableAppsDir%\CommonFiles\OpenJDK64 PATH=%JAVA_HOME%\bin;%PATH% Instead of running StartScript.bat to copy full Java directory to eclipse directory? :)
update to Eclipse 4.18
Eclipse 4.17 update
Home
Troubleshooting
Installation
Home
Installation
Home
Eclipse 4.16 update
Hi deb, I think I just fixed it by changing the temp folder to "/Data/tmp". As long as the folder exists this should be working. I also checked all paths Eclipse is accessing during a plugin installation by using the Sysinternals Process Monitor. I'll test and upload the changes soon.
Dear Berny, I am having problems multiple PCs to update Eclipse Portable (4.14 to 4.15) or install / update plug-ins (using 4.14 and 4.15). It fails in almost all cases with 'An error occurred while collecting items to be installed'. Digging deeper I saw that it all came down to a file exception in the error log: java.io.IOException: The system cannot find the path specified at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.createTempFile(File.java:2024) Eventually I...
Hi deb, thanks for the information. I changed some lines in the script and reuploaded the 4.15 installer. It should be working now :)
Hi Berny23, First of all thanks for the great tool. Unfortunately, the new startup script in 4.15 always copies the Java files at startup if you haven't installed into a root directory. Changing line 12 to 'if exist %CD%\App\eclipse\jre\bin\javaws.exe' takes care of that. Cheers, Deb
Hi Bokoblin, Thank you for your detailed post. As soon as Eclipse 1.15 is released, I will implement your script. I may remove the delay by default because it would annoy most users. But you could add an error message with a link to the wiki + a pause command if no jPortable folder exists. Kind regards, Berny23
First and foremost, if you are going to be using mklink it might be prudent to mention that Fat-32 does not support symlinks. Formatting USB sticks as Fat-32 is still very very common as it is more universal and is far easier to use when making bootable USB's. Even then, chances are high that someone will format it with Fat-32. Second, your StartScript is not working. If that is connected to %~dp0 not being useable with Fat-32 properly is something I'm unsure off. Regardless it did a poor job. Here's...
First and foremost, if you are going to be using mklink it might be prudent to mention that Fat-32 does not support symlinks. Formatting USB sticks as Fat-32 is still very very common as it is more universal and is far easier to use when making bootable USB's. Even then, chances are high that someone will format it with Fat-32. Second, your StartScript is not working. If that is connected to %~dp0 not being useable with Fat-32 properly is something I'm unsure off. Regardless it did a poor job. Here's...
Do note that symlinks do not work on Fat-32. For a Fat-32 compatible StartScript.bat, check out my post here: https://sourceforge.net/p/eclipse-neon-portable/discussion/bugs-errors/thread/6d1700a7cb/#a44f
Do note that symlinks do not work on Fat-32. For a Fat-32 compatible StartScript.bat, check out my post here: https://sourceforge.net/p/eclipse-neon-portable/discussion/bugs-errors/thread/6d1700a7cb/#a44f
First and foremost, if you are going to be using mklink it might be prudent to mention that Fat-32 does not support symlinks. Formatting USB sticks as Fat-32 is still very very common as it is more universal and is far easier to use when making bootable USB's. Even then, chances are high that someone will format it with Fat-32. Second, your StartScript is not working. If that is connected to %~dp0 not being useable with Fat-32 properly is something I'm unsure off. Regardless it did a poor job. Here's...
First and foremost, if you are going to be using mklink it might be prudent to mention that Fat-32 does not support symlinks. Formatting USB sticks as Fat-32 is still very very common as it is more universal and is far easier to use when making bootable USB's. Even then, chances are high that someone will format it with Fat-32. Second, your StartScript is not working. If that is connected to %~dp0 not being useable with Fat-32 properly is something I'm unsure off. Regardless it did a poor job. Here's...
First and foremost, if you are going to be using mklink it might be prudent to mention that Fat-32 does not support symlinks. Formatting USB sticks as Fat-32 is still very very common as it is more universal and is far easier to use when making bootable USB's. Even then, chances are high that someone will format it with Fat-32. Second, your StartScript is not working. If that is connected to %~dp0 not being useable with Fat-32 properly is something I'm unsure off. Regardless it did a poor job. Here's...
Dear Grunty, thank you for using Eclipse Portable. Did you install the latest "Eclipse Java Development Tools" package? Here is a short guide: https://sourceforge.net/p/eclipse-neon-portable/wiki/Install%20Features/ As long as you can start the portable Eclipse there should be no problem with your jportable version. If it's still not working please also tell me what operating system you are using. Kind regards, Berny
Dear Berny, thanks for your work on the portable Eclipse version 14.3, which I'm planning to use via USB Flash drives in class for my programming students. Nevertheless I can't get Eclipse to work properly, try as I might - Eclipse just offers me no Java build path, for instance, so I cannot edit or create any Java projects or even classes. Maybe this results in the fact the StartScript.bat doesn't create a link in the eclipse directory, so there's no jre accessible for Eclipse. If I try the workaround...
Hi, I had to change the script to made it work on my machine: mklink /J "%~dp0..\eclipse\jre" "%~dp0......\CommonFiles\Java64*jre1.8.0221**" I used jPortable64_8_Update_221_online.paf and Eclipse 4.12 Platform Runtime Binary [Portable].paf.
Thank you Berny23, This new version works perfectly. Great job
I now replaced the exe with a simple batch script, tested it in a Win10 VM and uploaded it on SourceForge (just redownload the latest version). I also fixed the workspace location and the upgrading process. Sorry for the mess :/
Installation
Installation
Installation
I'm using Windows 7 professional (SP1) I took a glance to EclipsePortable.exe located in "\App\StartScript" diectory but it seems to be an real EXE file rather a script file