I have eclipse rcp 4 application, which i migrating from mars to oxygen. It is a feature based application. All the required plugins are added to feature tab but some plugins like org.apache.batik.css, org.apache.batik.util and org.apache.batik.util.gui causing dependency issues. plugin tab by default taking 1.8 version of these plugins. But it seems that it has refer 1.7 version because if select only 1.7 from run configuration window application runs fine. Is there any way to make feature tab to select only 1.7 version instead of 1.8 permanently.? I tried to remove 1.8 version from eclipse plugin folder and it worked. But is there any better solution other than manually altering physical files?
Related
The option runAs->TestNG on xml file is missing somehow on my eclipse,
I tried to install the eclipse from scratch and now I have Version: 2018-12 (4.10.0).
Also I have latest JDK and JRE testNG is installed as far as I see and when I want to install them again I have a problem.
All the threads that i saw till now nothing helped me and i tried all the solution as i wrote maybe you have any idea
the only solution i founded till now is that i need to install eclipse from scratch and convert the same project again to TestNG and to copy the old XML to the new one, if its the latest eclipse than to download the beta version of TestNG
There is an issue with the TestNG plugin and Eclipse 2018-12 (https://github.com/cbeust/testng-eclipse/issues/408). You can use the current beta version from https://github.com/cbeust/testng-eclipse.
If the picture above of your installed software is the current state of your Eclipse 2018-12 setup, it cannot be a clean install. The version 6.14.x of the TestNG plugin is not compatible with 2018-12. It is not possible to install the plugin with Eclipse. Either the existing Eclipse directories are reused or the plugin directories have been added manually. It is important to remove them. After that, it should be possible to install the version 7 beta of the TestNG plugin.
It should look like this:
With this setup, you will get your context menu entry for TestNG:
I have some projects in my eclipse Luna that are based on Java 1.6 and I am trying to learn the latest spring boot which uses Java 1.8 , I am learning spring boot on spring tool suite which is based out of eclipse ,I tried installing Java 1.8 in my system and I have successful install both 1.6 and 1.8 Java in my system but when I try to open Spring tool suite it says JDK version should be 1.8 or higher I know I have the classpath set as 1.6 but is there anyway we can set the classpath 1.6 for eclipse Luna and Java 1.8 classpath for spring tool suite because I constantly change over projects as because Java 1.6 is my production environment in Java 1.8 is something like a test where I am trying to learn spring tool suite.
Is there any way we can achieve this without having to change the classpath everytime I Switch between spring tool Suite and eclipse Luna
The first thing to understand is that Eclipse itself requires a JRE to run (preferably a JDK), and that JRE can be different than the one that your projects in Eclipse are configured to use - they are intentionally separate.
To specify the JRE that Eclipse itself runs in, you should specify it in eclipse.ini. Read that page carefully, the format is very particular. Once you've done that, your system classpath or JAVA_HOME or PATH will not matter, Eclipse prefers its own ini settings.
With that done, the default JRE/JDK used for your projects in Eclipse will be the same as the one Eclipse itself is running in. But that's only the default, you can add more JRE/JDKs and configure individual projects to use them.
The point is, each instance of Eclipse can be configured to run in a particular JRE/JDK you have on your system (although there's really no reason not to use the latest for running all Eclipse instances), and then within each Eclipse instance, each project can be configured to use a specific JRE/JDK (which may or may not be the same one that that Eclipse instance is running in).
For example, you should probably configure both Eclipse Luna and STS to use the JDK 8 you have, via their .ini files. Then in Luna you can add a JRE config for JDK 1.6 on your system and set projects to use that one. The projects don't have to use the same JRE/JDK that Eclipse itself is running in.
we have a project which is compatible with GWT SDK 2.4 and Eclipse Indigo. I am trying to move to Eclipse Luna. Although I have made a progress, I couldn't get all of the features yet. Here is what I've done:
Downloaded Eclipse Luna and JDK 1.7 (both 64 bit)
Using install new software, installed last version of GWT SDK and
designer
Downloaded GWT SDK 2.4
Set this SDK as default (I copied some jars from SDK 2.6 in order to
do this)
After this installation, the project succesfully compiled and debugged. In addition, there are no problems with GWT Designer with my old ui.xml files. However, when I try to add new page I realized that Add New MVP view is gone. Is there a way to bring back this feature? Or can I copy from old Eclipse plugins?
I have successfully installed PMD in JUNO(Eclipse) but not able to see it in the properties.
I want to run the Project on PMD.
Actually the confusion point is that for PMD you have to enable it first by clicking on properties of each project.
select project-> Properties-> select PMD-> enable
This is the gernaral issue many have faced this. you can check screen shot in below answer as well.
After Installing PMD in Luna in Prespective it is Not Showing?
There are two PMD plug-ins for Eclipse: PMD for Eclipse and eclipse-pmd.
If you've installed the PMD plug-in using the Eclipse marketplace then you're using eclipse-pmd which requires Eclipse to run on a JVM version 7 or later. If you're running Eclipse on a JVM version 6 or earlier and you're using eclipse-pmd 0.7 or earlier the PMD property page won't be visible.
To solve this problem you have to run Eclipse on a JVM version 7 or later. To change the JVM on which Eclipse runs you have to set the parameter -vm in your eclipse.ini accordingly. The Eclipse Wiki explains how to specify the JVM.
Does anyone know where I can find the most recent feature comparison document for Spring IDE plugin vs SpringSource Tool Suite STS (version 3.3.0)?
I believe Eclipse made some good progress in Kepler release, (for example Maven support being shipped in) so was wondering if the feature gap between Eclipse+Spring IDE plugin and STS highlighted in 2.9.2 Feature Comparison were reduced in Eclipse Java EE Kepler.
There is not much difference now between Eclipse + Spring-IDE and STS. The main difference is that when you download STS, you are guaranteed that all the bits and pieces work together. When you install Eclipse + Spring-IDE, you may have some compatibility problems and trouble installing or upgrading.
My advice is this: if you already have an Eclipse that has custom plugins installed, then go with Eclipse + Spring-IDE and if you are starting from scratch, go with STS.