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.
Related
I have just reinstalled my OS and made a clean install of Eclipse.
I want to import my previous projects made on a previous version of Eclipse and that is no problem. However when I try to run it then it says: "The selection cannot be run on any server".
I read around I need to go into Properties => Build Path and do something there.
Only problem is my Properties menu does not have a Build Path option. I have searched around Eclipse for a long time now to find Build Path but stil no luck.
Does anyone now where og why my Build Path is no where to be found?
By Chance i found the solution myself.
I originally installed the Eclipse Php Mars version of Eclipse which i still can't get to work. But install the Eclipse Jee Mars (Java EE IDE) version instead solves the problem.
First time you run the code though you might have to run it through the main menu in the top and not by the convenient Run icon botton.
I have no clue why this is but now i can continue my work.
I have an Eclipse plugin that was originally written (not by me, and I don't have access to the original developer) that I'm trying to update for Eclipse Luna, because it stopped working when my team updated to Eclipse 4.4.
I downloaded the Luna Plugin development version, cleared a few warnings, updated some broken code, fixed a few bugs, and tested with "Run As -> Eclipse Application
This worked fine: all the views showed up, the preferences pages, etc.
So then I tried to export the plugin so I could test on a fresh installation of vanilla Eclipse Luna. I did that by using the Export Wizard:
And generated a deployable set of jars with said wizard:
I copied the generated folder (which contains all the jars appropriately) into the dropins folder of my fresh vanilla Eclipse Luna and started it up.
Unfortunately, I got the following error:
Which led me to this SO question and this Eclipse bug report, which explains that I have a 2.x style plugin that uses the plugin.xml instead of an OSGi style manifest.mf. Continuing my search, I found this SO question, which was directed at a 3.x version of Eclipse, but I used the 4.x equivalent:
Which I used with the following options checked:
And I accepted all the changes in the previous pane after the (long-running) changeset. However, upon deploying to my vanilla install, I got the same error about the plugin converter. That led me back to this SO question, which recommending installing the Eclipse 2.0 plugin support package. I did so and restarted Eclipse. The error in my error log did stop showing up, however the view/preferences/etc for my plugin are still not showing up. The plugin does show up under Help -> Installation Details -> Plug-ins, but doesn't seem to be interacting at all.
The text of the plugin.xml can be found here at Pastebin. The text of the MANIFEST.MF can by found at this other Pastebin link
Any suggestions for getting my plugin to work through the manual export so the other developers on my team can test my changes before I try releasing the update to the world?
I'm running Eclipse Kepler, JRE 1.7, with the e(fx)clipse plugin. Whenever I try to debug a JavaFx project, I receive the "source not found" stating the systemproperties class belong to the JavaFX sdk and doesn't allow modifications. I have tried to add this class to the step filter in eclipse with no luck. I have been unable I can find source code for JavaFX from Oracle. Is there any way to get past this and debug JavaFX in Eclipse?
There's never been a source zip of JavaFX2.2 released by Oracle because it was opensourced only partially.
I'd advice to use JDK8 which comes with the source code.
I have been receiving the following error and have done a lot of research and tried all of the offered solutions to no avail.
junitreport:
[junitreport] Processing C:\workspace\test123\junit\TESTS-TestSuites.xml to C:\Users\Matt\AppData\Local\Temp\null1903337257
[junitreport] Loading stylesheet jar:file:/C:/Users/Matt/Documents/Selenium/eclipse/plugins/org.apache.ant_1.8.3.v20120321-1730/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
[junitreport] : Error! The first argument to the non-static Java function 'replace' is not a valid object reference.
[junitreport] : Error! Cannot convert data-type 'void' to 'reference'.
[junitreport] : Fatal Error! Could not compile stylesheet
[junitreport] Failed to process C:\workspace\test123\junit\TESTS-TestSuites.xml
BUILD FAILED
C:\Users\Matt\workspace\Test1\build.xml:122: Errors while applying transformations: Fatal error during transformation
I found a solution at ant junit build error inside eclipse and saying that the issue was caused by a newer version of JDK and using 1.6_31 would solve it and I tried that following instructions I found online on how to change the version of Java eclipse is using. Every time I run the build ant it returns the same error regardless of which version of Java I am using. I have tried JRE7, jdk1.7.0_05, jdk1.6.0, jdk1.6.0_31 and others that I don't have installed anymore.
I am running the following
Windows 7 Pro SP1 x64
Eclipse IDE for Java Developers Version: Juno Release Build id: 20120614-1722
org.apache.ant_1.8.3.v20120321-1730
If anyone could provide any assistance in getting this report running it would be greatly appreciated. I'm new to programming and this is very frustrating especially since I'm still learning all of the jargon and trying to be sure I am following the instructions properly. If you require anymore information from me I will provide it and I will follow any instruction given to the best of my ability. Thank you very much in advance.
While an Ant Bug Report 384757 claims that this is caused by the XSL Tranformer build into the Oracle JDK - which may be true - the problem can be fixed by changing the Ant version:
I tried some of the workarounds mentioned there. After a while, I found that the bug appears with Ant 1.8.3 (distributed in Eclipse), but not with Ant 1.8.2 (distributed in Eclipse 3.7).
The bug also does not appear with Ant 1.9.0.
I have downloaded Ant 1.9.0 and in configured Eclipse's "Run As -> Ant build..." to use the Ant 1.9.0 folder as ANT HOME. This worked.
PS: My Eclipse used Ant 1.8.3 (which did not work), but running Ant from the console used Ant 1.8.2 (which worked). This was confusing at first.
I have solved the issue by downloading apache-ant-1.9.1 and configuring it in Eclipse by changing the ANT HOME from windows--> Preferences and setting the ANT HOME to apache-ant-1.9.1.
Below workaround fixed the build issue I had...
Download the 2 jar files from the urls given below and add those to Ant-Runtime Classpath located on Eclipse at:
Window>Preferences> Ant>Runtime>Ant Home Entries
http://www.java2s.com/Code/Jar/x/Downloadxalanjar.htm
http://www.java2s.com/Code/Jar/a/Downloadapachexmlxercesjar.htm
Restart eclipse and run the Ant build.
is it possible to use Eclipse 3.7 IDE for developing for the 3.5 platform? Or must I use Eclipse 3.5 IDE?
When I try to switch from Eclipse 3.5 IDE to 3.7 I get errors on projects, which were ok before:
Archive for required library: 'C:/.../.metadata/.plugins/org.eclipse.pde.core/.external_libraries/xyz/os/win32/x86' in project 'projectname' cannot be read or is not a valid ZIP file projectname
What do I have to do to exchange the 3.5 IDE with a current one, but still develop for the 3.5 platform?
I hope my explanation did make sense and was understandable :)
Additional Info:
- I never used the RCP before, now I must use it
- It's no option to upgrade the target platform (3.5)
- I searched the net and stackoverflow, but found no answers for using 3.7 and develop for target platform 3.5 (maybe nobody else has these problems or I used the wrong queries)
Cheers
Kai
Use the menu
Window > Preferences:
Plug-in development > target platform
Here you can add your eclipse 3.5 as a target platform, and then set it active.
But I don't think this will solve the errors you mentioned. I think those errors are because you are using the old workspace folder, and there is something not compatible with eclipse3.7. So maybe you can try to switch to a new workspace, and import your projects there.
I just resolved my problem :-)
In my case, there was a plugin jar, that contained the java sources:
jar
com
META-INF
src
plugin.xml
It seems like eclipse is putting jars inside of plugin jars in the following directory:
[WORKSPACE]\.metadata\.plugins\org.eclipse.pde.core\.external_libraries\...
For my plugin, it tried to put the src folder in this directory - which somehow failed.
After deleting the src folder inside the jar, the errors were gone.
RCP == bag of pain :-)