rcp

I am creating an RCP application, with many Greek messages, so everything is in UTF-8. As I develop and test through Eclipse IDE, everything is fine. When I am deploying through "Eclipse Product export Wizard" the resulting exe does not correctly display the Greek letters. I know that I am missing something stupid, but I have no idea what. Could you please help? (copied from the question - so this shows as having an answer) I found the solution although it was not as trivial as I anticipated. Eclipse gives the ability to control the build process with build.properties, in which you can specify

I am looking for the best practice of handling inter project dependencies between mixed project types where some of the projects are eclipse plug-in/OSGI bundle projects (an RCP application) and others are just plain old java projects (web services modules). Few of the eclipse plug-ins have dependencies on Java projects. My problem is that at least as far as I've looked, there is no way of cleanly expressing such a dependency in Eclipse PDE environment. I can have plug-in projects depend on other plug-in projects (via Import-Package or Require-Bundle manifest headers), but not of the plain

Is there at least anything other than Vogella's tutorials and his book , which is completely based on those tuts? Examples from his repo are often either incomplete/unfinished/won't run and those examples even don't match the book actually.. I'd like to find at least some javadoc for this, because any step to a side and I'm completely lost on how to accomplish different tasks and what functionality is available. Lars Vogel's Tutorials are the most complete and up-to-date documentation on Eclipse 4 development. Second to this is asking questions in Eclipse 4 Community Forum . Last option is to

I am creating an Eclipse RCP application. I am following Joel's advice in the following article "Daily Builds are your friend": http://www.joelonsoftware.com/articles/fog0000000023.html So, I've written a nice build script that creates an Eclipse RCP product and that runs unit tests on the code. All results are then distributed to the developer's list (after some grumbling). Now my next step, I want it to create the setup package that I normally create manually using the inno setup compiler. The question is, how would I get around creating this package automatically? I guess I can generate the

I am creating an RCP app which uses a host of third-party plugins. Some of these plugins contribute menus, menu items, and toolbar buttons that I do not wish to display. How can I determine which plugins are contributing these menus, menu items, and toolbar buttons and how can I disable them from doing so? tekumara To inspect details of menu, toolbar contributions etc. Load the Eclipse Plug-in Spy in your RCP application by including the plug-in org.eclipse.pde.runtime To inspect the current selection, press ALT-SHIFT-F1 To inspect menus, press ALT-SHIFT-F2 and then select the menu item Use

We have the code for an Eclipse RCP application in an Eclipse workspace containing multiple Java projects. We are using Mercurial with a simple .hgignore just *.class (but the same issue would pertain to Git). Even a small change to the code can result in many of the files in .metadata getting changed. I'd like to exclude some or all of the .metadata from version control. If we exclude it completely, the workspace is lost. Does anyone know what we can safely exclude? Alternatively, how can we recreate it if we pull the code down to a fresh computer? The files i'm personally aware of are:

I am trying to write a custom launch configuration while running a plugin project as an eclipse application. I have to run the plugin with limited dependencies. Is it possible to override methods in org.eclipse.pde.launching.EclipseApplicationLaunchConfiguration ? If yes then how do I do it ? You can't easily override the methods in EclipseApplicationLaunchConfiguration . That would require writing a new launch configuration - probably by using the org.eclipse.debug.core.launchConfigurationTypes extension point to define a new launch type. EclipseApplicationLaunchConfiguration always uses the