I just downloaded and installed Eclipse Kepler (Java EE version). Then I was hoping to install Maven Integration for Eclipse (Juno and newer) from Eclipse Marketplace.
I kept getting the error message "There is nothing to update".
Anyone knows what went wrong and fix?
I am not sure this question is allowed in SO. If not, let me know. I will delete it.
If you downloaded the EE version, then the m2e is already installed along with the IDE.
On another note, with concise question content and proper formatting, your question is allowed.
Related
While trying to install TesgNG in Eclipse 2019-03 . I got TestNG message as incompatible for Eclipse 2019-03.Is there any solution for this problem?
See a relevant issue: TestNG cannot be installed on recent versions of Eclipse via Eclipse Marketplace: "TestNG Eclipse plugin is under maintained, it's stable enough so you don't see much commit activities on the repo.
Feel free to create feature request and/or issue.
closing the ticket now since the Marketplace page is getting updated, thanks #cbeust"
I installed eclipse oxygen (4.7.0) "Eclipse IDE for Java Developers".
After installation I mentioned that "error log" view is not available any more.
I restarted eclipse multiple times and used also other workspaces.
How can I get back the error log view?
Did you try resetting whichever perspective you are using ?
(Window -> Reset perspective...)
I have found a solution: Just install Eclipse SDK by
Help->Install New Software...
After this is done restart eclipse and you got back the error log view.
The Error Log View is missing on a default installation of the Eclipse Platform Runtime. I assume this was missing from the "Eclipse IDE for Java Developers" package for Eclipse Oxygen either (I didn't test myself).
For sure, I'm experiencing this problem in 2018-09 and 2018-12 if I install the Eclipse Platform Runtime Binary (the bare-minimum Eclipse runtime I know of).
I opened bug 543120 for this.
I don't have tested the hexadez suggested workaround, because having to install the whole Eclipse SDK just to have this view is too much for me.
Another workaround I found is to install the bundle "Mylyn Context Connector: Eclipse IDE" from the 2018-09 or 2018-12 update sites: it's a much smaller compromise.
I can not see the Server option in eclipse, when I go to Windows-->showview, even in the --Others--option it's not there. I am using eclipse luna. Can anyone help me?
You have downloaded a package that doesn't include the server/web features. Instead, download Eclipse IDE for Java EE Developers.
Am trying to install Groovy/Grails Tool Suite (GGTS) for Eclipse into my Eclipse installation.
version of Eclipse installed:
Version: Luna Service Release 1a (4.4.1) - Windows 32-bit.
When I attempt to install ggts from the eclipse marketplace either by using the Eclipse Marketplace
menu option or by using the ggts drag to install button, the following window/error message is
obtained after selecting Confirm:
The following solutions are not available Groovy/Grails Tool Suite (GGTS) for Eclipse 3.6.4.RELEASE,
Proceed with the installation anyways?
How/can it be installed?
Thanks.
My bad. I forgot to put in the right (and versioned) update site into the Marketplace entry definition after the 3.7.0 release went out. This is fixed now. You should be able to install GGTS from the Marketplace again. Sorry for the inconvenience and thanks for pointing me at this here.
Keep in mind that there is no new GGTS version that is compatible with Eclipse Mars. The last version is 3.6.4 and is compatible with Eclipse 4.4 and previous versions.
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.