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.
Related
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.
I am working on a project in eclipse Juno. And I see that Eclipse has a latest version as Luna.
Can I directly Shift my Juno Project to Luna.?
or
do I have to make some changes.?
This depends on how large your project is, and how many technologies it uses.
I did this for an enterprise project, and the steps were pretty straightforward:
Setup the Luna IDE (i.e. install all necessary software from update sites and such)
Copy-paste your Juno workspace (keep the old one)
Launch Luna IDE with pasted workspace. Check for any compile errors.
If all is okay, then switch JDK7 to JDK8, and change the workspace compiler to 1.8
I would suggest to import the project in a new workspace with Eclipse Luna, then try to install all the plugins you need and check the project setup so that everything works.
With this way you always can open the old working workspace with Eclipse Juno while you're doing the migration.
Several tutorials mention that you can download spring in a tarball
and install it on your computer but when I go to the springsource
site all I can see is that you can download Spring Tool Suite
which is an eclipse plugin. So my questions are:
What if I wanted to work from the command line or an IDE other than eclipse?
The packages are available for Juno 3.8.2 or Juno 3.4.2, but how can I find
out my eclipse version? I've downloaded the most frequently downloaded version
of eclipse which is the one for Java EE developers but when I click on the Help
-> About entry I get:
Version: Juno Service Release 2
Build id: 20130225-0426
which does not match the eclipse versions on the springsource site 3.8.2 or 3.4.2,
so how do I know which plugin I need?
Thanks.
You can find out your Eclipse version by going to Help -> About Eclipse...
In the dialog that pops up, you will see something like:
Version 4.2.2
or
Version 3.8.2
If you downloaded the most commonly downloaded version, then you most likely have 4.2.2. The "Juno" release actually has distributions built for both 3.8.x and 4.2.x (a little complicated and confusing, I know). So, you should be able to install the Juno version of STS and be fine no matter what which version of Juno Eclipse you have.
EDIT
Your question is not very clear. I thought you were asking about how to install STS, but maybe you are asking about whether or not Eclipse is necessary at all. The answer is that of course, Eclipse is not necessary for Spring development, but it really is the easiest way to develop your spring apps (disclaimer, I am on the STS dev team).
There is no single way to just "downlaod the SpringFramework" because the framework is really just a very large set of jar files and their dependencies. Any single project typically only requires a subset of them as well as requiring other third party dependencies. For this reason, most people prefer working with a build tool like gradle or maven.
Probably the easiest way to get started w/o STS is to clone one of the sample projects from github. A list of the templates are available here: http://dist.springsource.com/release/STS/help/descriptors-3.0.xml which is obvioulsy meant to be consumed from inside of STS. But, you can use the file to grab links to the various github projects.
The Springsource Tool Suite (STS) is not required for developing with Spring. If the question is how you would install the STS, that's actually very easy. In Eclipse 3.7 (Indigo) or 3.8, 4.2 (Juno), click on the Help menu and select Eclipse Marketplace. If its not in the inital screen, use the find box type spring and click go which should bring up the the STS with the version of eclipse it is for in the title. Click install and the correct version and its dependencies will be installed for you. Try to use the eclipse marketplace for all the plugins you install, if possible. It makes things much simpler
Now that the new version of eclipse is out should I move to immediately? If my plug-ins work in Galileo will it work in the indigo?
There is no way to know without trying or researching what the particular plugin providers state regarding Indigo compatibility. Many plugins will work just fine. Some will not.
I would recommend starting a separate Indigo install along side your working Galileo install. Then install your plugins into the new install one by one. If everything installs and appears to be working, you can safely transition. If it doesn't, you will know which plugins are incompatible. Maybe a newer version exists or is on the way.
I am planning not to switch before SR2 is available. In the past new Eclipse versions had some minor bugs and I don't see the big advantage of Indigo for my daily work.
It is a risk worth taking. First, create a copy of your eclipse installation and upgrade and see if your plugins are working fine.
If those are working it's good to go Indigo.
All the best with Indigo.
I have been searching for a new IDE for a while. I finally decided to try Eclipse, although I am a little discontent with the memory usage, and I really like a lot of aspects about it. There are, as with learning any new IDE, some things that I haven't been able to figure out yet. One of the biggest ones is that it seems like no matter what plugin in I install it doesn't work, or doesn't appear to.
I downloaded Eclipse Galileo just to make sure that I could get plugins working there, since I know Helios is pretty new, and plugins worked in Galileo as expected. Is there something different that you have to do in Helios that I haven't discovered yet or am I missing something?
I have tried installing RSE, Subclipse, and Drupal for Eclipse (I am a Drupal developer). None of these work in Helios, but all work in Galileo.
Any help from Eclipse users would be greatly appreciated!
There's the new marketplace, so rather than using
Help -> Install New Software,
check out
Help -> Eclipse Marketplace.
I've had a similar issue with the m2eclipse plugin, but found installing it through the marketplace worked fine!