I use Eclipse 4.14 for an old RCP application that I updated to Java 8. Now it is possible to export the product but as soon as I add the feature "org.eclipse.babel.nls_eclipse_de" for the German language to the product in the "Contents" part the following error appears:
Processing inclusion from feature org.eclipse.babel.nls_eclipse_de: Bundle org.eclipse.ant.tests.core.nl_de_4.22.0.v20211218020001 failed to resolve.:
Host plug-in org.eclipse.ant.tests.core_0.0.0 has not been found.
The application do start in German. I only have problems with the export of the product.
Edit:
The run configuration noticed plug-ins are missing. Launching is possible. Export is not possible because of "missing" plug-ins. I do not understand why they are missing.
Screenshot of missing plug-ins
Related
Currently I am in the process of moving one of our RCP applications from an older version of Eclipse to the current version 2019-03.
Our application is feature based an makes use of the Birt report generator.
When trying to lauch the application via its product-file lots of unresolved plugin requirements appear, as the combination of RCP and Birt now seems to depend on different versions of org.apache.batik.* (1.7.0 and 1.8.0).
I can get the app running by manually enabling the different versions via Run -> Run Configurations -> Plugins. But of course this does not help when trying to export the RCP through the Eclipse product export wizard. The exported app is missing various plugins.
So I tried to manually edit the manifest.mf of the plugin that is dependent on birt:
Require-Bundle:
org.apache.batik.css;bundle-version="1.7.0",
org.apache.batik.css;bundle-version="1.8.0",
...
But this does not seem to have any effect on the plugins beeing exported.
The tip to switch back to a plugin-based project (How best to maintain an Eclipse RCP plugin target? 1 ) does not seem to work either.
So does anybody know how to get Eclipse to export all required versions of the org.apache.batik plugins?
Thanks a lot in advance!
Tom
I've downloaded the VisualVM source and am trying to compile the Glassfish plugin using Netbeans 7.01. Doing so results in the following error:
C:\source\visualvm\trunk\plugins\glassfish\nbproject\build-impl.xml:48: You must define 'nbplatform.VisualVM_100609-dd12ae64a19c.harness.dir'
That lead me to the project settings which shows the platform as "Netbeans IDE...". The drop down box is grayed out so I can't select the correct platform.
Yet, on my hello world VisualVM plugin I can set the platform to the appropriate platform and it runs great.
To try and resolve this I've tried creating platform.properties file and putting it in the nbproject folder with the following entries. However, this doesn't seem to be working
harness.dir=mypath/visualvm/visualvm_13
and
nbplatform.VisualVM_100609-dd12ae64a19c.harness.dir=mypath/visualvm/visualvm_13
Any suggestions.
Glassfish plugin is part of 'plugins' NetBeans modules suite. All modules from a Modules suite has to be build against the same version of NetBeans platform application (in our case VisualVM). This means that you can change the NetBeans Platform for the whole suite, go to the properties of the 'plugins' suite a change the platform there.
In order to build the VisualVM and it's associated plugins you must download the NetBeans platform and profiler binaries that are available on the VisualVM website's build guide section.
For example, to build the 1.3.2 release you would go to this section and download the NetBeans 6.9.1 platform and profiler binaries available through the link located on that page. The link I've provided also gives you instructions for obtaining the proper VisualVM sources from the repository and building VisualVM and it's plugins. For example, the sources for the 1.3.2 release can be checked out using the following url:
https://svn.java.net/svn/visualvm~svn/branches/release132
And once you've completed the checkout and extracted the NetBeans platform binaries (downloaded from the above link) into the
release132/visualvm directory, you can build the entire application and it's plugins by running ant build from the release32/plugins directory.
I successfully completed this entire process and can verify that the instructions work for 1.3.2. However, the instructions for building the trunk did not result in a successful build due to at least one missing dependency.
What the error that you were seeing was telling you was that the NetBeans platform's build harness could not be located. The harness is included in the downloadable binary and once you've extracted it into the release32/visualvm directory the values that are in the project.properties file will once again be valid. This is of course a good example of why you should keep everything needed to successfully reproduce a build in your repository!
I have implemented a graph editor with Eclipse EMF and GMF frameworks. After completing my project, I realized that this plugin shows dependencies (not explicitly added by me) on some OS-specific plugins.i.e:org.eclipse.ui.win32, org.eclipse.swt.win32.win32.x86. And whenever I have tried to bypass this dependency at my update site something went wrong with the installation process of the plugin.
As such it is impossible to run my plugin in *nix environment or even win64 machines.This seems a very heavy constraint dependency to me. Am I doing something in a wrong way? Or is there no other way of building Eclipse plugins which are cross-platform other than building the project from scratch at each different OSs?
We created a similar style of plug-in in my project. Under "Plug-in Dependencies" in Package Explorer I can see org.eclipse.swt.win32 listed, but it is not listed in required plug-ins in plugin.xml.
We also successfully created an update site which works for Mac users without issue.
So, yes it is possible to have a cross-platform plug-in.
I would suggest you first try to to use "Export..." -> "Deployable plug-ins and fragments" to create a bunch of jar files for your plug-in. See if these can be successfully installed by copying into the drop-ins folder of a fresh eclipse installation. Do this first on a Win32 install, then try on another platform. Once you have that working, use the new Eclipse installation to create the Update site.
I have a complex Eclipse Rich Client Platform GUI with 4 Eclipse plug-ins that I developed. I'm constructing it on Eclipse 3.5.2, Build id: M20100211-1343
It works just fine when I run it from inside of Eclipse as an Eclipse Application.
When I try to export the Eclipse Product using the export wizard on the Overview panel of the product file, I get this error:
'Export Product' has encountered a problem.
C:\BOPEclipse3.5RabId\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86.xml:100:
The following error occurred while executing this line:
C:\BOPEclipse3.5RabId\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86.xml:345:
C:\BOPEclipse3.5RabId\.metadata\.plugins\org.eclipse.pde.core\temp\assemblyLocation\tmp\gui\plugins\org.eclipse.equinox.launcher_1.0.201.R35x_v20090715 not found.
The following error occurred while executing this line:
C:\BOPEclipse3.5RabId\.metadata\.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\package.org.eclipse.pde.container.feature.win32.win32.x86.xml:345:
C:\BOPEclipse3.5RabId\.metadata\.plugins\org.eclipse.pde.core\temp\assemblyLocation\tmp\gui\plugins\org.eclipse.equinox.launcher_1.0.201.R35x_v20090715 not found.
I looked at the directory location given in the error. The equinox launcher plug-in is there.
The version 1.0.201.R35x_v20090715 matches the version in the error message.
I have the equinox launcher plug-in, and the win32.win32.x86 platform fragment in the Dependencies list of the product file.
I have the "The product includes native launcher artifacts" check box in the Overview panel of the product file checked.
I have org.eclipse.equinox.launcher in the list of Required Plug-ins in the Dependencies panel of the GUI plug-in XML.
I added "javacDefaultEncoding.. = UTF-8" to the first line of the build.properties file of the GUI plug-in. (I found this advice on a Japanese blog.)
I have cleaned the plug-in projects multiple times.
Edited to add what I tried today:
I created a new Eclipse 3.5 instance. Didn't help.
I copied the workspace and tried to use Eclipse 3.6. Same error, different line numbers.
I created a Hello World RCP and tried to package it on Eclipse 3.5. Same error. I used a different workspace. Same error.
I created the same Hello World RCP and tried to package it on Eclipse 3.6. Same error.
End of today's edits.
I've searched eclipse.org and the Internet.
I'm hoping that one of you has encountered this problem before, and can point me to a solution. If I ever figure out how to solve this problem, I will post the answer.
I think I've found the solution.
I can package the Hello World RCP if I set the JRE System Library to Java 1.5. I get the error when I set the JRE System Library to Java 1.6.
It's going to take a couple of days to convert my real RCP application to Java 1.5. I hope this solves the problem.
I've reported this problem to the Eclipse Foundation. It's bug number 337,235.
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.