I use Eclipse for everything. Python, Django, GWT, Android... But when you install all the plugins, Eclipse becomes very slow.
Is there a way that I can set it up so that there are two or more icons for Eclipse in the Applications directory, each for specific task?
Thanks
Developing in Eclipse for the past few years, I've found it's just easier to have several copies of the Eclipse directory, one for each kind of development I do (Android, java app, Grails). It's sometimes cumbersome installing new versions of Eclipse or new versions of the common plugins (Subclipse, etc), but it does make Eclipse start-up MUCH faster.
Simply create another install directory for Eclipse, with another shortcut to it, and only install the plugins you need for that dev environment. I use a different workspace for each one, though I'm not sure that's necessary, as long as you're using the same version of Eclipse for each install.
Related
Who knows how to customize your own eclipse? I want to include some plugins and use it as bundled solution and not to install additional plugin when I want to use it on other machine.
This is what I've done in the past.
The first thing you have to do is a fresh install of eclipse, all the plugins you intend to use, and their configurations. After that just copy the eclipse folder AND the workspace/.metadata folder (this one could be an hidden folder) to the new machine.
Copying those folders to a new machine and running eclipse with the -clean flag (only needed the first time) seems to work fine so far.
I ran into some problems when trying to use 32bit eclipse in an 64bit environment, but I guess it's normal that it doesn't work. Also, this is not a cross-platform solution, i.e you cannot use your Mac installation of eclipse in Windows, or vice-versa.
I think you are referring to so called Individual Source Bundle, which you can build and create your own setup that will install your custom Eclipse bundle on desired machine.
Another solution would be just creating simple install/archive that will unpack c:\eclipse\ to c:\eclipse\ (or whatever) on target machine. This will work since Eclipse is not hardware dependent (but sure, it is OS dependent) because it's Java based.
I was wondering, is there a big difference between the pre-tuned versions of eclipse, like th pdt and the one for c++ developers and so on?
Or is it absolutely the same, if I take the classic version and add all the plugins I need? I am going for a project, that will have a mix of python, html, css, javascript and php in it.
Theoretically, there's no difference between the pre-installed versions of Eclipse and adding all the plug-ins you need to Eclipse classic.
However, the Eclipse "Install New Software" functionality doesn't always work perfectly.
My suggestion would be to download the Eclipse for PHP developers, and add the Python and JavaScript plug-ins.
Once you've determined that the Eclipse plug-ins meet your needs, and before you start your project, zip up your Eclipse and save it. There are times when your Eclipse gets corrupted, and having a zipped Eclipse with all the plug-ins makes restoration faster.
HI all,
I have Eclipse installed with PDT (PHP Development tools).
I want to program in Java and C++, do I have to download whole Eclipse JDT and Eclipse CDT again, and have separate installations, or can I install "plugins" to handle Java and C++ ?
Thanks
Yes you can install the plugins into the same Eclipse installation. For Helios you can use the Update manager Help->Install New Software then select the Helios site and select C/C++ in Programming Lagnuages and so on. If there's something else you need you need to get the update URL and add a new site.
You can have one eclipse with all the plugins (and perspective). But that's tedious:
you'll have to find the plugin jars for each of the 'suites' and place it in the plugins dir. Sometimes they might not have an update site url
some plugins cause problems, sometimes mixing certain plugins cause problems - in short, the more plugins, the more likely your environment will crash
The way I'd suggest is to have a separate eclipse installation for each task. I myself have 3, for different sort of java development (one java, one flex, one for specific project with specific plugins)
Eclipse itself is perfectly stable and capable of supporting quite a lot of plugins. However if you are unlucky to need "crappy" plugins, there the problems being.
I like to carry software around with me on a USB flash drive. I also like to work in both Windows and Linux. Finally, I like to develop software using powerful tools.
Bringing these three things together, I want to be able to carry an IDE around with me. My favorite choice is Eclipse.
So, I tried to get an Eclipse install working on a thumb drive. Not surprisingly, it's just fine if I pack in a JDK. But Eclipse without plugins just doesn't do it for me. After installing my plugins of choice, I had a hefty 300ish MBs of data.
Then I realized that I'd only installed for Linux. And that I was going to have to duplicate everything to get a Windows install. That's not good.
I've searched the web. I found a guide on creating .link files which looks like a hack from the early 80s. I found documentation on the new Eclipse p2 provisioning which I couldn't even understand. I checked Pulse, and they don't support Helios yet.
I remember in old Eclipse days you could just install a plugin to an alternate directory, and share that dir across different Eclipse installs. Today, I couldn't manage to find anything of the sort.
I did manage to get Netbeans up and working properly in a cross-platform manner in around 30 minutes. But I prefer Eclipse.
Could anyone give me a hand? What I'm looking for is:
One install of the platform-independent portions of the Eclipse internals
One install of each plugin I desire
The ability to run this unified Eclipse from both Linux and Windows
I know I'll need a JVM for each platform. I know I'll also need an SWT lib and launcher for each OS. That's fine.
You need to have separate Eclipse installations for each platform and a shared plugins directory for both installations. There are many questions on the subject on StackOverflow. For example, see this comprehensive answer.
Start with the standard Eclipse packages. Complete your shared dropins setup. Once you are up and running, you get probably move plugins from each standard installation to the shared dropins directory to save space (for example, JDT).
Eclipse can contains a lot of different feature set via plugins.
Do you install all the plugins in one single eclipse? or do you install STS from spring, Flex eclipse from adobe, or even RCP development bundle from eclipse.org, every eclipse variant handle its task respectively?
Which way do you prefer and why? speedy response? avoid the hassle of updating/installing plugins?
Thanks
If you have enough power on your workstation (and the right eclipse.ini), you can:
install all the major plugins in one operation (choosing the most complete distro, like the J2EE one)
install any other external plugins in a shared directory (meaning those plugins will continue to be referenced by any new version of eclipse distro you may install in the future)
In eclipse I prefer to install them separately, because it seems to keep things running smoothly, no upgrading things as they come along, only as a whole thing, it makes for a lot of duplication though... With Netbeans (which I prefer) I generally install everything in one place and it too runs smoothly, even when I upgrade different plugins and add and remove other ones.
I separate groups of related plugins/features by defining separate install locations (You used to be able to do it through the IDE, can't find the right button at the moment, see here for some guidance on doing this manually). That way you can enable/disable groups if you need to.
The install locations can also be shared between different Eclipse installs (with care!), and if you completely trash or want to upgrade Eclipse, you can redefine the eternal locations on the new install, no downloads needed.