Eclipse is quite self contained and the launcher seems to work well even when Eclipse restarts (Task Manager shows it's still running, ie didn't start cleaning up)
The update released via the updater to the main Eclipse are mostly bug fix only, meaning no portability breaking changes should be introduced and most of the Official plugins on Eclipse's site are portable as in saving settings only in the workspace and the main Eclipse dir.
The only exception is if a plugin decides to store stuff outside of the workspace or if the plugin uses an Eclipse feature that saves stuff outside of the workspace the gluxon didn't portabilize. (Like the secure storage for example)
This is actually bug 326642 over at Eclipse.org, and just to say, I completely support the built-in updater. So there shouldn't be any problems with it.
Think like a [Files\DirectoriesMove] Section from the PA.c launcher.
Altough you can really make it have any syntax you wan't.
But the point is, that it should allow you to specify any path to a file or a directory (including multiple entries) to be backed up to the data folder.
This will allow the user to add handling to any plugins that decides to store stuff outside of the workspace (Like in %userprofile%).
Erroneous error message at installing : Not enough free space
Hi,
I'm just a minor issue of no consequence.
As I installed the Eclipse 3.6 Classic PAF via the PortableApps launcher, I got an error message about not having enough space on the target device. Stille the intaller let me continue with a form displaying available size and where to pick the install path.
That form accurately indicated 18MB for installation and 4GB free.
So the initial warning is erroneous. I guess it finds that 4
Why is there a "Portable Eclipse" Project, when you could just use the original non-Portable version on your USB Drive?
I do use it, and i've posted my own "Portable Eclipse" in this forum. You just have to create 1 executable that prepares the proper environment for the Eclipse. In my case, it would just configure the JAVA JDK path so that the Eclipse could find it and start.
One of best thing about my solution, is that you can use the latest eclipse version as soon as it is out from the Eclipse web site.
I think that the Eclipse Developing Team should be aware of PortableApps so that it should save all user info on the workspace or some other "Portable" location, otherwise from that:
What other features does this "Portable Eclipse" version bring that explains the reason to create a special project for it?
As with anything here, it's in PortableApps.com Format. This means that you can easily use it with the PortableApps.com Platform, Backup, etc. That is one of the requirements for anything here.
Then too there are some useful things like drive letter updating which you won't get with normal Eclipse. That's what a launcher can do.
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
You question has been answered many times before. The launcher allows Eclipse to be integrated into the Portable format and detect Portable compilers, such as MinGW Portable or NSIS Portable. It also automatically updates drive letters in open files you're editing when switching computers.
One of best thing about my solution, is that you can use the latest eclipse version as soon as it is out from the Eclipse web site.
Exactly who said you can't do that with this? You plop the new version into the App\Eclipse folder
BTW, onto another question, I realize the flood of new PortableApps is starting up again. Can Eclipse Portable join that flood? (I'll be willing to make any changes, except for updating it to PAL)
I don't have that problem, i always reference my workspace as "..\workspace", this allows me to always have the workspace relative to the eclipse instalation path.
Anyways... i wish you the best with this project.
As a developer, count me in if i can help.
They reside under the %userprofile% directory if I remeber those plugins, this is why I suggested gluxon to add support for specifying arbitary folders in the ini to be backed-up by the launcher.
This will allow solving those cases with third-party plugins storing stuff outside the workspace.
Thanks to the contributors of this forum, I was able to set up my Portable Eclipse 3.6 with Wascana and veditor plugins.
Now for the testing (on WinXP):
First, I tested my installation by building a C++ test program.
Then, I closed Eclipse and PortableApp.
Next, I manually changed the drive letter.
Finally, I again ran Eclipse and rebuilt the test program.
The program runs but there were warnings due to some INCLUDE directories having the wrong drive letter. There were basically two sets of INCLUDE directories, with the only difference being the drive letter.
Does anyone know how to set Eclipse to automatically remove include paths that are associated with an old or no-longer-in-use drive letter?
(I can manually delete the entries through the project's Properties.)
I get that all the time. In fact, I get it twice every time I start.
At times, at least in the past, I've been able to fix it by closing everything before I exit, and then when I start it again, it's not a problem, but it comes back quickly.
Despite the strange error message, it seems to be harmless ...
The messagebox's title is "Open File", and it has the eclipse icon.
I think this may have something to do with where other stuff is installed on the host computer.
I have my portable apps primarily on my laptop, and periodically use rsync to update a desktop machine from the laptop. The laptop doesn't get this error, but the desktop does.
Eclipse is quite self contained and the launcher seems to work well even when Eclipse restarts (Task Manager shows it's still running, ie didn't start cleaning up)
The update released via the updater to the main Eclipse are mostly bug fix only, meaning no portability breaking changes should be introduced and most of the Official plugins on Eclipse's site are portable as in saving settings only in the workspace and the main Eclipse dir.
The only exception is if a plugin decides to store stuff outside of the workspace or if the plugin uses an Eclipse feature that saves stuff outside of the workspace the gluxon didn't portabilize. (Like the secure storage for example)
updating eclipse today, and I'll post some feedback.
confirmed.
whats interesting is that the folder has 1 folder which has 1 folder which has 1 folder which has 1 folder which has 1 file:
H:\opt\public\technology\epp\epp_build\36\eclipse.S-3.6RC4-201006031500\artifacts.xml
weird.
This is actually bug 326642 over at Eclipse.org, and just to say, I completely support the built-in updater. So there shouldn't be any problems with it.
Thanks for reporting the bug though segev208.
The trigger for this bug seems to be changing the drive letter, as in changing a computer.
What do you think about adding the ini value for handling plugins that store stuff outside of the workspace.
Sure, good idea, but how do you think that should work?
Think like a [Files\DirectoriesMove] Section from the PA.c launcher.
Altough you can really make it have any syntax you wan't.
But the point is, that it should allow you to specify any path to a file or a directory (including multiple entries) to be backed up to the data folder.
This will allow the user to add handling to any plugins that decides to store stuff outside of the workspace (Like in %userprofile%).
I tried installing it multiple times, but it ain't a workin'
or if it is, I can't start a new NSIS project, and when I open up an NSI, there is no syntax highlighting.
EDIT: I'm using Helios
EDIT 2: Restarted Eclipse, now it works just fine
Hi,
I'm just a minor issue of no consequence.
As I installed the Eclipse 3.6 Classic PAF via the PortableApps launcher, I got an error message about not having enough space on the target device. Stille the intaller let me continue with a form displaying available size and where to pick the install path.
That form accurately indicated 18MB for installation and 4GB free.
So the initial warning is erroneous. I guess it finds that 4
Thanks. I think you should report that bug to John T. Haller though, since it's a PortableApps.com Installer problem.
Why is there a "Portable Eclipse" Project, when you could just use the original non-Portable version on your USB Drive?
I do use it, and i've posted my own "Portable Eclipse" in this forum. You just have to create 1 executable that prepares the proper environment for the Eclipse. In my case, it would just configure the JAVA JDK path so that the Eclipse could find it and start.
One of best thing about my solution, is that you can use the latest eclipse version as soon as it is out from the Eclipse web site.
I think that the Eclipse Developing Team should be aware of PortableApps so that it should save all user info on the workspace or some other "Portable" location, otherwise from that:
What other features does this "Portable Eclipse" version bring that explains the reason to create a special project for it?
As with anything here, it's in PortableApps.com Format. This means that you can easily use it with the PortableApps.com Platform, Backup, etc. That is one of the requirements for anything here.
Then too there are some useful things like drive letter updating which you won't get with normal Eclipse. That's what a launcher can do.
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
That drive changing feature would come in handy. Nowadays i just use the inbuilt "substd" to create a fixed "V:" Virtual Drive...
You question has been answered many times before. The launcher allows Eclipse to be integrated into the Portable format and detect Portable compilers, such as MinGW Portable or NSIS Portable. It also automatically updates drive letters in open files you're editing when switching computers.
Exactly who said you can't do that with this? You plop the new version into the App\Eclipse folder
BTW, onto another question, I realize the flood of new PortableApps is starting up again. Can Eclipse Portable join that flood? (I'll be willing to make any changes, except for updating it to PAL)
Java is still being finalised with Oracle. After that we'll see about it.
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
I don't have that problem, i always reference my workspace as "..\workspace", this allows me to always have the workspace relative to the eclipse instalation path.
Anyways... i wish you the best with this project.
As a developer, count me in if i can help.
I have two plugins that always right to the local user Application Data directory. Google GWT and ADT both do this.
they add:
.android
.google
[Changed from a reply to a standalone comment - use "Add comment" at the top, not "Reply" on a comment, for this case - mod Chris]
What's the full path?
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
They reside under the %userprofile% directory if I remeber those plugins, this is why I suggested gluxon to add support for specifying arbitary folders in the ini to be backed-up by the launcher.
This will allow solving those cases with third-party plugins storing stuff outside the workspace.
Sorry forgot to post that.
The two directories (not files) are created and remain in the user directory:
C:\Documents and Settings\User\.andriod
C:\Documents and Settings\User\.google
Another abnormally is the Blackberry plugin prompts for Microsoft Visual C++ 2008 Redistributable Package (x86).
Eclipse Helios also wants permission to open the firewall. I think Google wants usage feedback.
So these plugins could be a nightmare.
Thanks to the contributors of this forum, I was able to set up my Portable Eclipse 3.6 with Wascana and veditor plugins.
Now for the testing (on WinXP):
First, I tested my installation by building a C++ test program.
Then, I closed Eclipse and PortableApp.
Next, I manually changed the drive letter.
Finally, I again ran Eclipse and rebuilt the test program.
The program runs but there were warnings due to some INCLUDE directories having the wrong drive letter. There were basically two sets of INCLUDE directories, with the only difference being the drive letter.
Does anyone know how to set Eclipse to automatically remove include paths that are associated with an old or no-longer-in-use drive letter?
(I can manually delete the entries through the project's Properties.)
Thanks.
Upon open, I received the message. Any idea how to fix this?
I get that all the time. In fact, I get it twice every time I start.
At times, at least in the past, I've been able to fix it by closing everything before I exit, and then when I start it again, it's not a problem, but it comes back quickly.
Despite the strange error message, it seems to be harmless ...
Happens to me only on first-run once. Then it never occurs again unless I delete my Data folder.
Is this comming from Eclipse or Eclipse Portable? You should be able to tell by looking at the MessageBox title.
why? did you have a message box like that in the launcher?
No, I've never seen it, that's why I'm asking if it's a problem on my side (launcher).
I think this is coming from Eclipse itself.
The messagebox's title is "Open File", and it has the eclipse icon.
I think this may have something to do with where other stuff is installed on the host computer.
I have my portable apps primarily on my laptop, and periodically use rsync to update a desktop machine from the laptop. The laptop doesn't get this error, but the desktop does.
Pages