I use this version of Eclipse for quick edits of php files for different websites I maintain. These files are not part of any project recognized by Eclipse, just random files I bring in and out of Eclipse.
Anyway, this is my problem: I open a file in Eclipse, I write "This", save it, and close it. I open the same file in Notepad (for example), I then edit it to say "This sucks", save and close the file. Then when I reopen the same file back in Eclipse, Eclipse only shows the updates I last made in Eclipse, i.e., "This". It doesn't reflect the changes I made in Notepad. How can this be fixed to where it doesn't cache files and opens files in their current state?
I tried Windows->Preferences->Remote Systems->File Cache and set Maximum Cache size to 0, and clicked "Clear Cached Files". This does not help, and I suspect this is dealing with something else (if it is, additional information on what this relates to would be appreciated).
Eclipse for PHP Developers
Version: 1.3.2 - Helios Service Release 2
One last note. I thought v. 1.3.2 seemed old, because I thought it was in v. 3.*, so I reinstalled Eclipse for PHP with the latest version on the Eclipse website and I ended up with the same version..
It is a bug of DLTK and according to https://bugs.eclipse.org/bugs/show_bug.cgi?id=367757 it will be fixed on the next/future version.
Ver.1.3.2 is the version of EPP(Eclipse Packaging Project), it indicates the version of "Eclipse for PHP Developers" all-in-one package. It is too old anyway. You are using Eclipse 3.6.2(it's 3.7.1 now), PDT 2.2.1(it's 3.0.0 now), DLTK 2.0.0(it's 3.0.1 now), ... (as for PDT, newer doesn't mean better though)
FYI, there is a patched file for DLTK 3.0.1 (not for any other versions) about this problem at http://sourceforge.jp/users/atlanto/pf/eclipse/files/?id=435 pdt_tools.feature_patch.dltk.3.0.1.v20111005.zip
try disable "Window->preference->Network Connections->Cache."
It's work for me, as before I have to use external tool (configure vim) to save php file, in eclipse juno.
Related
To upgrade to a new version, the eclipse FAQ suggests to add a new repository and then install available updates. Upgrading to Neon, the corresponding repository is http://download.eclipse.org/releases/neon/.
On this page, it says:
NOTE: Due to structural changes you cannot update from a Mars (or prior) all-in-one package to a Neon version. If interested in the technical details, see bug 332989 and bug 490515.
I still tried to above procedure, but no updates were found. What is the best way to upgrade from Mars to Neon? A complete new installation? How do I preserve my settings?
The note on the repository page is right. Thanks to your report, I edited the FAQ to make it clear that upgrading packages from Mars to Neon is not supported.
Instead you need to to a fresh install for Neon (or later).
I tried to upgrade in the recommended way, by adding the repository links and doing an update, but then I got a lot of conflict messages. I foolishly tried to remove the conflicting software components, until it told me that Eclipse itself was the conflict! I posted my problem to the Eclipse Forums, and was told by a regular with tens of thousands of posts that Neon was so different that I should not even try to upgrade, just create a new installation. When I tried to do that however, I got lots of warnings "That the artifact download is progressing very slowly from ..."
It is not possible to upgrade from Mars (or earlier versions), so a new install is needed.
This can be in parallel with the old install. From the FAQ:
Fresh install
If you prefer not performing an update (for example
because some 3rd-party content isn't ready for the current release of
Eclipse IDE so the update reports conflicts), you can still download a
fresh install of the Eclipse IDE and install it in another location on
your filesystem, and use it together with the previous version.
To do so, download a new build from the Eclipse download Web site
(https://www.eclipse.org/downloads/eclipse-packages/) and run the
installer or unzip the archive in a new directory. We strongly
recommend against installing/unzipping over your existing version of
Eclipse IDE as it may corrupt your installation.
When you start a new version of Eclipse IDE, you can use the same
existing workspace folder that you were using with older version. The
workspace will be migrated to newer version and Eclipse IDE will to
reuse all configuration. The workspace is forward compatible
I have an existing Eclipse library tool -- quite an old one -- running on Eclipse 3.4, and I would like to add in Aptana Studio. However, the current download specifies that it requires Eclipse 3.5 or better. A colleague of mine has Aptana running in his exactly the same version of the same tool -- presumably he got an older version that would work on the older Eclipse.
Can I download a version of Aptana to plug in to Eclipse 3.4?
Or, if not, can I grab the copy of Aptana from my colleague's machine and drop it into my own Eclipse?
Note that there are specific reasons why I need to use this older version of Eclipse, so replies along the lines of "upgrade your version of Eclipse to 3.5 or later!", while undoubtedly well-intentioned, won't be much use to me....
Edited on November 30: it is Eclipse 3.4 which I have, and I originally put 2.4 by mistake (which doesn't even exist!).
You can grab the Studio's from your colleague's machine. The Studio is pretty much contained to the folder it's installed at (with some minor exception that should not stop you).
No packages are available for 2.x.
Cheers
In the past I've always downloaded the new version, and then manually reinstalled all of the plugins I use - but this is tedious in the extreme.
Is there a way to upgrade Eclipse "in-place"? How do I do this exactly?
The approach below worked for me, and seems to be the easiest. It's from this eclipse FAQ and slightly modified for clarity:
For upgrading from Eclipse 3.5+ to 3.6+
Help -> Install New Software
Enter the release update site url eg. 'http://download.eclipse.org/releases/indigo' <- if upgrading from 3.5 or 3.6 (Helios) to 3.7 (Indigo)
Click Add
Click Cancel
Help -> Check for Updates
Note: The original URL has changed. (I've left the original link for posterity)
following the NEW FAQ instructions
Also you may have to remove any incompatible updates plugins before proceeding.
(For Example: JBoss Tools has different versions for Helios and Indigo that are incompatible)
Update: I didn't try this when upgrading from 3.x to 4.x (Juno). I just set up a whole new workspace. I think I read somewhere that doing that is the safest approach to upgrading major versions.
As of 3.7 (Indigo), you may export/import install configurations via the
File > Import/Export > Install menu.
This allows you to install a new release of Eclipse, point it at your
existing workspace, and install your plugins from an older installed
copy.
If you always download all plugins manually and then deploy it by copying to dropins folder, then while migrating to newer version, just need to copy that folder to the new eclipse.
And even not all plugins will support newer version of Eclipse so I guess there is no really easy way available to do the migration.
The answer is, there is none. It's pointless to speculate here as to why the Eclipse community chooses not to make one. They haven't.
Please take a look here:
alt text http://img16.imageshack.us/img16/2810/errrp.jpg
Why i got that error when i'm trying to update my Eclipse Galileo to the newest Eclipse M6 Helios?
I'm using the update URL from here:
http://eclipsesource.com/blogs/2010/03/14/eclipse-3-6-m6-helios-available-for-download/
Is this a bug? If not, what can i do?
Please help. Thanks!
Can you try the upgrade process after re-launching eclipse with the -clean option?
Do you confirm you are using the http://download.eclipse.org/eclipse/updates/3.6milestones/ update site address?
What version of eclipse are you using (3.5, 3.5.1, 3.5.2?) and what extra plugin did you installed?
For instance, if you have installed Scala for Eclipse, you could not upgrade AspectJ which could block the upgrade process. (see this thread for illustration)
To summarize the 3-days span and 15 comments below:
An easiest path to solve this would be:
have a fresh installation of Eclipse, especially the Java EE Helios package (see Helios packages)
with an eclipse.ini including a -data /path/to/existing workspace
( That way, you have 2 Eclipse referencing the same Eclipse projects. You can launch one or the other, and if the new one does not work, you can still revert to the old one. This is safer than trying modifying extensively -- through the update process -- your current Eclipse)
add the GlassFish plugin for Eclipse
(download both the plugin and feature jar files, quit Eclipse, then copy the unzipped contents of the first into the plugins directory and the second into the features directory of your Eclipse installation)
Check you Java EE JDK if needed
And here you go: you should be able to see a GlassFish Server and integrate it as a target runtime there.
I've got my Eclipse 3.4 envirnoment set up nice and cozy the way I like it. Took me some time too, to find all the plugins (Mylin, PDT, Subclipse), set all the settings, etc. Now I see that some of the plugins (like PDT) only support 3.5 in their latest versions.
Is it possible to update from 3.4 to 3.5? I'd hate to do it all again.
I read in some mailing list where they noted that it's possible, but the conversation trailed off in another direction. Google wasn't much help, and Eclipse's documentation either.
All of your settings are actually stored as part of your workspace. So you could do a fresh install of the latest version of Eclipse, add the extra plugins that you want (many of which will have newer versions for Eclipse 3.5) and when you launch, just make sure you point to your old workspace.
Help -> Software Updates... -> Available Software tab -> Add Site...
Enter the update site for the Galileo (3.5) release train: http://download.eclipse.org/releases/galileo
Now go back to the Installed Software tab and click the Update... button.
After some computation you should be presented with a list of available updates (or some cryptic errors about how your current environment cannot be updated due to compatibility issues).
This is what I did.
1.- My workspace was in c:\Users\me\workspace.
I copied this folder to c:\users\me\eclipse\workspace-3.4 and to c:\users\me\eclipse\workspace-3.5
So now I have twice the same, just with different names.
2.- Extracted eclipse-SDK-3.5-win32.zip to C:\program files\eclipse-SDK-3.5-win32
3.- Run Eclipse 3.4 and changed the workspace from c:\Users\me\workspace to c:\users\me\eclipse\workspace-3.4. Then I closed Eclipse.
4.- Run Eclipse 3.5 and selected c:\users\me\eclipse\workspace-3.5 as the workspace location (you can also use the -data argument I think).
5.- Downloaded and installed the PDT plugin (I develop in PHP).
And "Voila", now I'm able to run Eclipse 3.4 and 3.5.
BTW, even if I had to install the PDT plug in, I didn't had to touch the configuration. It took the former one from the workspace folder.
There is some information at help.eclipse.org/galileo/index.jsp, look in Workbench User Guide\Tasks\Upgrading Eclipse.