Can't install winrun4j eclipse plugin - eclipse

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.

Related

run as testNG is missing

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:

Eclipse Mars 1.0 Build Path Missing From Properties Menu

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.

Eclipse Maven Build Error

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.

spring development - with or without eclipse + checking eclipse version

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

Eclipse Java EE - Galileo - Unable to view plugins

I am new to Eclipse so I am having a hard time troubleshooting this problem. I have a new installation of Eclipse Java EE - Galileo on Windows, and I am unable to see any changes made in the IDE after installing plugins. I have verified that the plugins are installed via installation details, but see no changes made.
For example, after installing the maven integration plugin m2eclipse I go to File->New->Project ... and I have no option for maven. After installing the QuickRex plugin I have no view for it etc.
I have tried re-installing the plugins, re-installing Eclipse, and starting Eclipse with the -clean option, but nothing has resolved the issue.
Any ideas? Thanks!
Ok. This is just a wild guess but could you start over with a fresh install and make sure that you uncheck the option Contact all update sites during install to find required software as shown below:
alt text http://img717.imageshack.us/img717/8039/screenshot003ao.png
I faced a similar problem (on another platform than yours), some updates were "disabling" all my plugins. Not checking this option allowed me to work around this issue.
Follow-up: You'll need to install that Zest stuff manually from the GEF update site:
alt text http://img339.imageshack.us/img339/8003/screenshot003rl.png