I am developing an Eclipse RCP product in Eclipse e4 environment using Kepler for RCP developers on 64-bit Linux and Java 7.
I'd like to use Eclipse Babel language packages within my Eclipse product. Copying features and plugins directory into Eclipse IDE directory works without a problem. I can run my Eclipse environment in the language I want by passing -nl argument.
I used PDE to produce a product and applied the same step by simply copying the language package into the product's features and plugins directory. However, it did not work as I see OK and Cancel button labels still in English.
Is it correct to simply copy the files or do I have to add an extra dependency?
Thanks.
Related
I am using eclipse 4 application platform for building custom ide like app, but i am still not sure what libraries i can use.
For instance i can't find some API which is responsible for maintaining projects.
Is it even possible to create project or this is just part specific for eclipse as IDE and can't be used if i am using e4 rcp?
The org.eclipse.e4.rcp, org.eclipse.emf.core and org.eclipse.emf.ecore Eclipse features list all the plugins that a pure e4 application uses.
The list includes most of the org.eclipse.core.xxx plugins but not the org.eclipse.core.resources plugin which contains the workspace code (things like IFile and IWorkspace).
So if you want projects and workspaces you would have to write you own code for that - which would not be compatible with any other Eclipse 3.x plugins.
Eclispse Luna has been just released. I wanted to grab it from the download site. But here comes my problem. Even the Standard and Java Developer versions have features built-in which are not needed for me and just slows down the IDE. For example i do not use Mylin or Plug-in development. These things cannot be deleted from the installation... Is there an Eclipse Luna release which only contains the basic package?
Look at the Eclipse Project downloads
The Eclipse Platform is the smallest (but does not even have Java development).
The Eclipse SDK has Java and Plugin development and the Eclipse source. This is the one I always start from.
I have a Java project and a C project. I would like to use the Eclipse IDE to work on each project. To accomplish this I ended out downloading a version of ecliplse for C and a version for Java. Seems like I should only need 1 ide and then "switch perspectives" when I switch to work on a different project. However, the "Java" perspective is not available in the dropdown when the C version of eclipse is running, and vica-versa.
Do I really need two ides?
Download one IDE. Go to the Eclipse Marketplace and install the other one. It will have both plugins installed for a single Eclipse IDE installation.
No,
you can easily install the CDT features in a Java version of eclipse, or vice-versa, but I would add C++ to Java.
Once the features are installed the C++ projects can be opened and it is indistinguishable from the prepackaged version.
There is no magic there.
Help --> Install New Software --> Select helios repository (with a version indicator)
wait till the package list appears
Open the Programming Languages folder and select the CDT packages.
Typically eclipse complains so;e dependencies are missing, so select those too and it'll install.
I have a simple RCP Plugin (with a product) and I want it to run in atleast Linux and Windows (32 and 64bit). I have a product that contains a Feature from which buckminster uses to create the p2.site. (I only use a build.properties and buckminster.properties files, no *.cspec and *.rmap files, since these probably get generated by buckminster from the RCP product/feature files).
My problem is that my feature has a link to the 64bit linux swt plugin (I'm running 64bit linux) but if I add references to the windows swt plugins to my RCP .product the buckminster build fails to resolve these plugins and then does not export the p2.site correctly.
How do I get buckminster to build the p2 site by looking at the dependencies of my RCP .product file and if it doesn't resolve the win32 or win64 swt libraries from my workspace that it will look else where for these dependencies?
I like the idea of buckminster determining my project dependencies from my .product file so I don't have to keep a .cspec and a .product file in sync, when I make changes to my project's dependencies. If the dependencies are not found on my workspace then I want buckminster to find the missing dependencies (could be all of them if running from Hudson server) from "maybe" a .rmap etc
You have to execute your site.p2 target several times, to provide a build for each platform.
See the tutorial on the Eclipse wiki or on Ralf Ebert's blog about more specific details.
What are the differences, specifically, between the Java EE and RCP versions of Eclipse?
And how would one essentially get a "combined" version that includes all the best goodies for plugin development along with the best tools for Java EE?
I think what I'm looking for is the ability to create a "merged" instance entirely through the p2 updater. For example, if I open up a Java EE instance of Eclipse, open a java file, hit alt-shift-f1 to bring up plugin spy, and then click on "compilationuniteditor" to view the source of the java editor, I get .class. But in the RCP version, I get the source. How do I get those things in the Java EE editor using the normal Eclipse update mechanism? That's my goal here. What plugins in update manager contain what "essential bits" for each distribution.
Another example is installing all the Examples plugins. In the RCP distribution, you can easily install them from the "Welcome" page. So how, in the Java EE distribution, could you do the same thing?
The problem I'm trying to solve here is that I want to get away from maintaining two separate instances of Eclipse, since I do a fair amount of work in both RCP (for plugin development) and in Java EE (for webservice stuff, etc).
I started with the Eclipse for RCP Developers and used the "Help > Install New Software..." Feature to add in the "Web, XML, and Java EE Development" tools from the "Galileo" update site.
You may want to be a little choosier than I was and maybe exclude the "Rich Ajax Platform" and possibly the "PHP Development Tools" Features from the category.
It's better to use the "Install New Software" feature than to try and merge directories. The dependencies can be fairly complex and troubleshooting a merged directory can be a nightmare. Let p2 do the heavy lifting.
You can get a full comparison of all eclipse distros here.
Basically, the J2EE one includes the RCP ones, except for the fact that the RCP has the sources of some plugins, and not just their binaries.
To get a mix of the two, load them both, unzip them, and then compare the content of plugins and features sub-directories of both installations (with WinMerge for instance).
Copy any extra RCP files into the J2EE directories, and that should be enough.
From my understanding, the Java EE version comes with plugins for developing java programs whereas the RCP version includes the minimum number of plugins to build a rich client application.
These links should help:
http://wiki.eclipse.org/RCP_FAQ
http://wiki.eclipse.org/index.php/Rich_Client_Platform