I am beside myself with this error and can't make any progress until I get past this issue.
I have the latest STS (Spring Tool Source) 3.7.1 specifically for Eclipse Mars 4.5.1. I deleted all my old versions of STS, and deleted my old .eclipse file as well since I wanted this to be a fresh install. I also went into my c:\Users\Tom Holmes\AppData folders and removed all traces of 'Spring Tool Suite'.
I installed the new latest STS 3.7.1 for Eclipse (Mars) 4.5.1 and pulled down the latest Subclipse for the Eclipse (Mars) 4.5.1. I opened to my old work space which was fine before, and now whenever I try to use STS to run a maven build I get the error listed below.
Error: Could not find or load main class Holmes.sts-3.7.1.RELEASE.configuration.org.eclipse.osgi.25.0..cp.;.C:.Users.Tom
I have tried everything I can think of to re-loading the projects into a new workspace, to deleting the projects and re-downloading them.
Ultimately I find in the workspace .metadata plugins directory under m2e.eclipse.core there are no lifecycle mappings? Does that matter?
How can I re-create this, or is this more of a maven/sts problem?
So, here is what I found ... Since STS 3.7.1, specifically for Eclipse (Mars) 4.5.1 was the issue ... I tried several other versions of STS.
I tried STS 3.7.0 for Eclipse (Mars) 4.5.1 which does work. When I installed this, I immediately got notified that there was an update ready. The update was specifically for the m2e Maven-Eclipse Integration.
I also tried 3.7.0 for Eclipse (Juno?) 4.2.2 which also does work, and again this was looking for an update, and again was for m2e Maven-Eclipse Integration.
My feeling is that, specifically STS 3.7.1 for Eclipse (Mars) 4.5.1 was broken as far as the m2e plugin. Since the m2e changes are embedded in this latest version, something must not have been right. The other versions that I downloaded and installed all worked fine. For any of these versions, there was this upgrade for the m2e (Maven-Eclipse) integration plugin ... but in this case, the update worked.
You know, I like STS, I think it works great. After updating several times, like anything else, it can get "jinky" and then I decide that maybe I should just download a new fresh copy of the tool which usually works great.
Clearly pulling this update into the latest version just didn't mesh well. But now I am up and running, and hopefully SpringSource will fix this issue.
I really hope this helps someone else out.
I would recommend installing a regular Eclipse distribution and then installing STS as a plugin. There should be plenty of instructions online that explain how to do it. I've been using this approach for years and never had any problems.
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'm having issues installing the WinRun4J eclipse plugin. Eclipse finds the plugin just fine and begins the installation, but most of the way through the install eclipse stops at an error. The error is below. I've tried googling for a resolution to this error for the better part of 30 minutes, but I can't find anything that works. Aside from googling I've restarted eclipse multiple times and run it as administrator. No luck. How would I resolve this error?
Here's my eclipse info:
Eclipse Java EE IDE for Web Developers.
Version: Mars Release (4.5.0)
Build id: 20150621-1200
This looks like the update site is invalid. It also looks like this software is no longer maintained. Your best bet is to download the eclipse plugin jar directly and place it into your eclipse/dropins folder.
You can download the latest plugin jar here. Be careful, though, looks like this hasn't been touched in 6 years.
To upgrade to a new version, the eclipse FAQ suggests to add a new repository and then install available updates. Upgrading to Neon, the corresponding repository is http://download.eclipse.org/releases/neon/.
On this page, it says:
NOTE: Due to structural changes you cannot update from a Mars (or prior) all-in-one package to a Neon version. If interested in the technical details, see bug 332989 and bug 490515.
I still tried to above procedure, but no updates were found. What is the best way to upgrade from Mars to Neon? A complete new installation? How do I preserve my settings?
The note on the repository page is right. Thanks to your report, I edited the FAQ to make it clear that upgrading packages from Mars to Neon is not supported.
Instead you need to to a fresh install for Neon (or later).
I tried to upgrade in the recommended way, by adding the repository links and doing an update, but then I got a lot of conflict messages. I foolishly tried to remove the conflicting software components, until it told me that Eclipse itself was the conflict! I posted my problem to the Eclipse Forums, and was told by a regular with tens of thousands of posts that Neon was so different that I should not even try to upgrade, just create a new installation. When I tried to do that however, I got lots of warnings "That the artifact download is progressing very slowly from ..."
It is not possible to upgrade from Mars (or earlier versions), so a new install is needed.
This can be in parallel with the old install. From the FAQ:
Fresh install
If you prefer not performing an update (for example
because some 3rd-party content isn't ready for the current release of
Eclipse IDE so the update reports conflicts), you can still download a
fresh install of the Eclipse IDE and install it in another location on
your filesystem, and use it together with the previous version.
To do so, download a new build from the Eclipse download Web site
(https://www.eclipse.org/downloads/eclipse-packages/) and run the
installer or unzip the archive in a new directory. We strongly
recommend against installing/unzipping over your existing version of
Eclipse IDE as it may corrupt your installation.
When you start a new version of Eclipse IDE, you can use the same
existing workspace folder that you were using with older version. The
workspace will be migrated to newer version and Eclipse IDE will to
reuse all configuration. The workspace is forward compatible
I am sure somebody might have come across this scenario.
I have many working sets in my present workspace (Eclipse Helios version). I am trying to migrate the same to Indigo SR2 version.
Simple workspace migration from one version of Eclipse to another also I have not done earlier.
Please let me know how to proceed with the same
Normally, everything should go fine when you install all the plug-ins in Indigo which you have in Helios. Then you just open your workspace with Helios, you are good to go, but of course, a full workspace compilation might be done.
As far as I know, Indigo used to have some problems with Maven support, I don't know if it has been fixed.
In the past I've always downloaded the new version, and then manually reinstalled all of the plugins I use - but this is tedious in the extreme.
Is there a way to upgrade Eclipse "in-place"? How do I do this exactly?
The approach below worked for me, and seems to be the easiest. It's from this eclipse FAQ and slightly modified for clarity:
For upgrading from Eclipse 3.5+ to 3.6+
Help -> Install New Software
Enter the release update site url eg. 'http://download.eclipse.org/releases/indigo' <- if upgrading from 3.5 or 3.6 (Helios) to 3.7 (Indigo)
Click Add
Click Cancel
Help -> Check for Updates
Note: The original URL has changed. (I've left the original link for posterity)
following the NEW FAQ instructions
Also you may have to remove any incompatible updates plugins before proceeding.
(For Example: JBoss Tools has different versions for Helios and Indigo that are incompatible)
Update: I didn't try this when upgrading from 3.x to 4.x (Juno). I just set up a whole new workspace. I think I read somewhere that doing that is the safest approach to upgrading major versions.
As of 3.7 (Indigo), you may export/import install configurations via the
File > Import/Export > Install menu.
This allows you to install a new release of Eclipse, point it at your
existing workspace, and install your plugins from an older installed
copy.
If you always download all plugins manually and then deploy it by copying to dropins folder, then while migrating to newer version, just need to copy that folder to the new eclipse.
And even not all plugins will support newer version of Eclipse so I guess there is no really easy way available to do the migration.
The answer is, there is none. It's pointless to speculate here as to why the Eclipse community chooses not to make one. They haven't.