New: LibreWolf (Dec 03, 2022), Platform 23.0 (Dec 9, 2022)
450+ real apps (49GB), 1 billion downloads, Please donate.
OUTDATED: This release of Eclipse Portable is now outdated, please to go the new thread for the latest release.
Thanks for the new update! Too bad the download file isn't getting any smaller.
-adude159753, adude1597535, thorn, essentiel
--whomever you choose to remember me by in the previous and current games I have and am playing.
-Word to the wise: Only with hard work can you do; only with persistance can you achieve.
I didn't have time to compress this.
Takes half an hour to.
And the John's new installer is making the file bigger. By 20 MB.
Then you're doing something wrong. Take a look over it again, and I'll see if I can fit time in to look at it tomorrow or the day after.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
As you can see, the installer has an option to install additional languages, probably making the installer that much bigger.
May the Shwartz be with you
That must be it.
I counted the installed space without the langs. And they're...
56.3 MB (59,052,410 bytes)
So that solves it
Just a note, once you UPX compress EXEs and DLLs they often won't compress as much with LZMA (which the installer uses), so you wind up with a slightly larger installer. The install size is less, of course.
Sometimes, the impossible can become possible, if you're awesome!
increased by 20MB? hehe wow. It's not a good idea to UPX post install but would have been a nice solution
It shouldn't be that big a difference (a few percent usually). UPXing post install is a bad idea as it's really slow on flash drives. Better to do it once up front and save everyone the install time.
Announcement says: 205 MB download / 181 MB installed
The installed size is 20 MB smaller, but gluxon forgot the 56.3 MB languages. So it's 181 + 56.3 MB installed.
Should I be counting installed size with the langs though?
You list both like we do on the app pages. So 181-237MB installed.
For the 3rd time...
What do I have to do to get this into Pre-Releasing!!!!
We need some testing results and then we can flip it to a pre-release.
Don't forget to update your forum topic name and link to the download with the new version number.
BTW - What is classic edition?
the Eclipse Platform, Java Development Tools, and Plug-in Development Environment, including source and both user and programmer documentation.
Other Eclipse packages are available here.
I'm a Java programmer and I like your Eclipse Portable.
The newest Dev-Test1 is very good ,thank you for correcting working directory bug.
Good work ^^
Um... sorry about saying this like almost a month later, but could you make it go through the testing?
Portable Apps are located on my USB drive in a folder containing spaces in folder name. As a consequence, Eclipse Portable doesn't find Java Portable in "CommonFiles" folder and doesn't start at all. Would you please check your NSIS script and add double quotes to $PORTABLEAPPSDIRECTORY variable to prevent and correct this issue ?
Keep going the good work !
Okay, thanks for reporting
I'll update and post as soon as possible.
BTW, I programmed it to look for local java if it doesn't find it in the CommonFiles. Shouldn't that work?
Portable Apps are located on my USB drive in a folder containing spaces in folder name
Why?... just curious.
I've been working in the IT business and I'd like to have working applications in any configuration. That's why my Portable Apps are installed in a folder with spaces in folder name. If an application doesn't handle this use case properly, it always shows rapidly
The problem is bigger than that...
It's this line causing the problem.
ExecWait '"$PROGRAMDIRECTORY\$PROGRAMEXECUTABLE" -vm $JAVAPATH $Parameters $ADDITIONALPARAMETERS'
I can't put double quotes in a ExecWait. I'd create errors.
I'll try to find a workaround though.
use single quotes outside, double inside.
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
Double quotes are fine within ExecWaits. I usually do something like this:
ExecWait `"$PROGRAMDIRECTORY\$PROGRAMEXECUTABLE" -vm "$JAVAPATH" $Parameters $ADDITIONALPARAMETERS`
Unless of course Eclipse doesn't like em. But ExecWait is fine with the above.
Heh... I just thought the two quotes would conflict... turns out they don't
I'll post the dev test 3 when I add the RunLocally.
Note the single quotes I used are the angled ones. I recommend these for stuff like this.
` vs '
Welcome back gluxon.
I'm not sure its a good idea to release only eclipse classic since people are guarnteed to want a few of the more common versions (Java and C\C++) and will probabley spam about it.
Even if you can easily install the extra plugins from the other versions using Eclipse's built in plugin\update manager or swapping the Eclipse app dir.
Its fine for now since its a dev-release so you wont have to compress and upload a gigabyte of data to sourceforge (Although you may want to test to make sure the other versions work to)
Maybe just post all the packages when It becomes official.
Developement Test 2 Released
Seems to be a problem with your links
There appears to be a problem with your links. It's not going to the download pages.
I'm deeply sorry. It should be working now.
Your NSIS Plugin link directs tot he Classic Edition download. Also can I ask what is the classic edition?
See the Eclipse site. They have multiple bundles including one for Java devs specifically and other stuff. Classic, I think, is what used to be standard (just about everything).
See, I knew I put the classic download in there! Just in the wrong place when I was updating the links
A new release of eclipse is avalible and the portable version needs to be updated.
I also still think that you need to make the eclipse packages from the main eclipse website avalible.
Since some of those package come with specific components and installing them all manually is just annoying.
Perhaps by downloading them from the eclipse website and placing them in the app folder.
Like a launcher only release.
Beleive me, packaging those huge files are even more annoying
I've decided to wait for when this is official to package all those on the main Eclipse website.
3.5.1 Portable was just released. Probably being uploaded while you made this comment (At school).
Seriously what does it take for an app to become official...
It didnt even progress to pre-release stage...
Also i still think a portable JDK that resides in common files will be useful.
EDIT: Please also note that the latest version seems to also use a local Java install.
I haven't had time to test whether it will prefer the local or the portable common files and/or jdk folder copy. make sure it prefers the portable common files and the jdk folder copy over the local one when they exist.
It should be using the local java install, if the current Java Portable is not installed any where on the drive.
I want it in pre-release too But the dev team is dead.
And Um... you can replace JDK in the Common Files from your local JDK install. Should be compatible.
Not dead, resting.
I'll add this to the list.
You just reminded me... I should have started a new thread (new eclipse)
Only start a new thread if you've got over a page or so, or normally when you have gone up from DT to PR. New versions, please keep them in the same thread.
Development Test 3 Released.
I'm going to whine now...
I don't think there's any more to do on this!!!
I just open up Eclipse Portable to edit it's own source and just stare at it...
There's nothing left to do!!!!!!
Is that you saying you think we're ready to go on this one?
I'll make a effort for you tommorrow. No promises, but I really hope to get it done.
First of all, I want to compliment you. This is a very good release. Alas, I did find somethings, so let's cover them:
. . . Code . . . .
(and immediately underneath)
You don't need to do that. You can, but you don't need to. See lines 106\108, 118, etc.
All in all, a very good test. I'm very please at the way this has turned out. Fix those issues that were marked to be fixed, and consider the other ones. You don't have to change those, but you can if you would like.
Do that, post it, I'll give it the quick once over and I'll stamp it with my seal. (I has to make a seal? Hmm . . . .)
Okay, all fixed. Anything else? I feel like I did nothing... and I didn't make any major changes...
Always minor things, you did really well. I"m curious why you got the errors, I'll have to look at everything (but I won't bar a release because of that). I forgot to check it adjusting things across drive drive locations, I'll do that when you post this newest version. I figure if you worked on developing it, you've got that working, so I don't think that they'll be any issues there.
Code Issues: Notice I said "consider". You don't have to change it.
I guess if you don't display a splash screen, you don't need the ending code. I should have checked whether you did the splash screen or not, my bad. John will have to comment on whether or not we can change their splash screen. At any rate, you'll have to recompile it for pre-release 1\final version with the new splash screen, so I don't see it being an issue.
That's a good thing
I'll get working on compressing all the other Eclipse bundles and stuff
You rock Oliver!
I don't see anything wrong with that, I treat each label like a paragraph, each with a different objective. I don't like merging two different codes that do two different things in the same label. (You probably know this, but it won't go to a label unless you tell it to jump to it.)
Actually, NSIS will move to the next label in line...always. There's no need to always specify a GoTo. That just clutters up code and adds to the size (it won't hurt, but there's no reason for it).
Well, I feel reluctant on removing it but.. okay..
Thanks for that info
I just tried it. It gives the "Warning, label GetRoot was not used" or something like that.
... just comment out the not used labels.
.... You missed my point...
Gizmokid2005 + OliverK
Would it be ok to leave it just the way it is? I like it organized and it's easier for me to manange and write my launcher...
It doesn't affect speed or functionality too.
You may leave anything I said as consider changing alone. Note the consider. You only have to change what I said you need to change. You may leave the gotos and label, etc.
I'll say it this way:
Forget about the goto's and labels I won't gig you for it.
A ; makes it less organized?
Let's quit picking. Seriously, I had no idea that my suggestion would be used to slap him. The code works and that's what matters.
Let's let him post his fixes, then I'll certify it, and gluxon can be a full developer as well.
I don't think its necessarily a matter of coding style. I think what matters is that at the end of the day, it functions.
And perhaps, just perhaps, he's used to another type language that uses it.
It didn't slap me in the face If it did it's because I made a big deal out of it.
And... I already posted the fixes...
One, more thing... Would it be a good idea for the launcher to detect when eclipse is doing updates and update the launcher itself?
What do you mean you already posted the fixes?
I just got what you meant...
Okay... I'll post Dev Test 4 in a couple minutes.
I was saying that removing the Goto ThisLabel would create errors... then you came and told me to comment out "ThisLabel"... Which was kind of the opposite of what I was saying.
I told you not the opposite, I gave you a solution (but you missed the point)
That produces the errors:
And here's my suggestion without warnings:
I wasn't trying to comment them out...
I was saying that if I remove the GoTo it'll prevent the label from being executed...
OK, here is the gist of it.
StrCpy $1 "Dummy filler line of code"
StrCpy $1 "Now we're here."
If you only ever go to NextStep once, then you might as well do the following, which is simpler, neater, more descriptive, and less prone to bugs (the less code you have the less there is to be buggy):
StrCpy $1 "Dummy filler line of code"
;=== Next step
StrCpy $1 "Now we're here."
(The ;=== bit is just a nice clear way of identifying a block of code, and is used by PortableApps.com launchers for convenience and consistency.)
For a bit of explanation, gluxon; in NSIS, each Section is evaluated if selected (and for our purposes, the main section is selected). The code will go through from the start of the section, and flow however it flows (i.e. following Gotos, function calls, etc.) until it gets to an Abort, a Quit, a Return, or the end of the section, when it runs out of things to do. Your label is just sitting there doing nothing, and so it's better with the goto and the label out of the way.
what line? what is the exact error
Well, as you know each label needs to be specified and declared with GoTo or something else like IfFileExists, StrCmp, etc.
Gizmokid2005 said it would automatically jump to the next label without a goto, which does not happen...
Well, wait for the release team and their test reports and maybe then you'll have to whine for various reasons
Yeah.. once they get this going, I'm going to whine about getting it going faster... lol
*Just joking, I wouldn't rush the release team ;)*
Development Test 4 Released!!!
This is the version that includes the small fixes found by OliverK.
(Haven't fixed labeling yet... I just realized that and it's already uploaded... and labeling won't mess with the functionality or portableality of the program, just tidyness with people who wish to edit the launcher.)
Awesome. I shall review and be handing out tah seal at some point soon.
New Mirrors Added!
It gives me great pleasure to bestow my goofy graphic upon this release
You has Tah Seal of Approval
Downloaded It'll be put on my site soon!
If that's fine with you of course
yeah, you can post it on the eclipse page
I found some people who actually get this app from that page. Considering the link is in like... the 10th page when you google "Eclipse Portable", it's very surprising.
[Edit: Scratch that, the 14th page.]
Okay... so um... now what?
wemake sure JOhn KNOW THAT THIS IS READY!
I've filed a request that this be not released until we get the SVN issue sorted out in the Universal Launcher. There's too big a security liability with it at the moment. I'll get back to you on it when I get somewhere with it (step one: wait for John's first release of PAUL).
I didn't even know Eclipse had a SVN system. That and I don't think that a PAUL will EVER carry what a REAL developer needs in his toolbox.
Eclipse has a couple of SVN plugins available which are used quite a bit. (Subclipse and Subversive.) gluxon made it so that $APPDATA\Subversion would be handled (can't remember if it was conditional on the plugin being installed).
I don't quite savvy the rest of your message... I plan on making sure that PAUL can swing such things easily.
OliverKThat and I don't think that a PAUL will EVER carry what a REAL developer needs in his toolbox.
Chris MorganI plan on making sure that PAUL can swing such things easily.
Sorry to say that, but your pet "PAUL" will never make things easy. If you create an universal launcher which can handle everything, it'll be too complex to configure. Guess you'll have several hundreds of INI-lines for configuration and thus several hundreds options for BUGS. If you create a basic launcher which is easy to configure, almost no developer will use it. It's easier to code a few lines to do the fancy things that most apps need to be portable.
My apps will never switch to an universal launcher. :evil:
Just my 2 cents.
AWWW, you bully!
Yes, I read the message, but as of Dev 4, it neeeeds JRE to be inside of it's directory (Eclipse that is) and Open Office doesn't look there. How do I get it to look for JRE in my CommonFiles, because it won't. I tried to just use another release, or something like that (c++ for ex) but I guess they all depend on it. Can someone please help me and send me an email at firstname.lastname@example.org
I can never seem to follow these posts as much as I do my email.
There should be a way to be notified on more posts
What? It's working fine for me.
I did bump around where Eclipse Portable looks for java first though, when Dev Test 4 came out.
What error do you get if java is not in EclipsePortable\App\Java?
Or is it the other path? EclipsePortable\App\Eclipse\JDK?