I want to update my Eclipse so that I can associate projects with Tomcat 7. Currently, when I go to Window > Preferences > Tomcat, I get the following.
I originally thought it was a Eclipse version issue and I'd have to update. But I have Indigo and a friend of mine has Helios (older) and he has the Tomcat 7 option.
Then I thought the Tomcat feature might have been a plugin. So I tried Help > Check for Updates, but there were no updates.
Does anyone know how to get Version 7.x to appear?
Finally figured it out.
Close Eclipse.
Go here and download the latest zip file to get the plugin. Inside will be a folder called com.sysdeo.eclipse.tomcat_v.v.v (v.v.v depends on which zip version you downloaded).
Look inside your eclipse/plugins folder and delete the old com.sysdeo.eclipse.tomcat_v.v.v file.
Copy the new com.sysdeo.eclipse.tomcat_v.v.v file (from the zip) into the eclipse/plugins folder.
Restart Eclipse.
And there you go :)
Related
EDIT 2014-02-07: Eclipse Luna is here, and support for Tomcat 8 is included in the bundled WTP : ) Happy days!
Tomcat 8 is still in development, but you can get it here. Now there is a RC version on the main Apache Tomcat page. Update 2/27/14: 8 is released now, and adapters built for WTP, just not integrated into eclipse bundles yet. Soon!
In Eclipse Kepler though, there is no supported adapter in the add server list for Tomcat 8. the Tomcat 7 adapter doesn't work, and it doesn't look like there's a new extension for it to download in the "Install new Extension" dialog.
Is my only option to get it (Tomcat 8) running locally outside of Eclipse and maybe hook a remote debugger into it for stepping through code? Will that even work for Eclipse Kepler + Tomcat 8? IntelliJ IDEA 12 couldn't do it in the 30 minutes of time I put into that path.
If you're wondering why I'm trying to do this at all, I'm playing around with Spring 4.0.0.M1 and 4.0.0.M2 WebSocket stuff. They (per Rossen Stoyanchev's Spring 4.0 blog post and examples) use JSR-356, which is implemented in Tomcat 8, theoretically to be back-ported at some point to Tomcat 7.
An answer to the broader question of "How can I easily get a development environment going for Spring 4 WebSocket support?" would be nice, but it would also still be nice to know how to plug in unsupported web servers to Eclipse.
Cheers,
E
**Update 8/7/13 - Rossen Stoyanchev updated the Spring 4.0.0.M2 blog and added some jpda wisdom and shared that yeah, he's using remote debugging:
That said, it's not very hard to debug with Tomcat 8 inside Eclipse. Just change the last line in bin/startup.sh to be (note the addition of "jpda"):
exec "$PRGDIR"/"$EXECUTABLE" jpda start "$#"
Inside Eclipse create a remote debugging configuration for localhost port 80, launch it after starting Tomcat, and you can put breakpoints in the source code.
Thanks Rossen!
**Update 9/29/13 - Eclipse Kepler SR1 just arrived, but alas! No WTP support for Tomcat 8. Tomcat 8 is up to RC3.
**Updates 12/5/13
Blog url fix.
Tomcat 8 up to RC5.
Bug to track WTP fix in Eclipse to support Tomcat 8 HERE.
IntelliJ IDEA new version 13 says it now supports Tomcat 8. Haven't tried yet personally.
UPDATE: Eclipse Mars EE and later have native support for Tomcat8. Use this only if you have an earlier version of eclipse.
The latest version of Eclipse still does not support Tomcat 8, but you can add the new version of WTP and Tomcat 8 support will be added natively. To do this:
Download the latest version of Eclipse for Java EE
Go to the WTP downloads page, select the latest version (currently 3.6), and download the zip (under
Traditional Zip Files...Web App Developers). Here's the current link.
Copy the all of the files in features and plugins directories of the downloaded WTP into the corresponding Eclipse directories in your Eclipse folder (overwriting the existing files).
Start Eclipse and you should have a Tomcat 8 option available when you go to deploy.
I follow Jason's step, but not works.
And then I find the WTP Update site http://download.eclipse.org/webtools/updates/.
Help -> Install new software -> Add > WTP:http://download.eclipse.org/webtools/updates/ -> OK
Then Help -> Check for update, just works, I don't know whether Jason's affect this .
The only thing the eclipse plugin is checking is the tomcat version inside:
catalina.jar!/org/apache/catalina/util/ServerInfo.properties
I replaced the properties file with the one in tomcat7 and that fixed the issue for eclipse
In order to be able to deploy the spring-websockets sample app you need to edit the following file in eclipse:
.settings/org.eclipse.wst.common.project.facet.core.xml
And change the web version to 2.5
<installed facet="jst.web" version="2.5"/>
This should be a comment under the accepted answer, but I don't have 50 reputation yet.
At http://download.eclipse.org/webtools/downloads/
I first selected Released 3.5.2, which like others did not work for me.
Then I picked Integration 3.6.0, and saw Tomcat 8 for New Project of Dynamic Web Project.
I have tried below and it worked for me.
In eclipse go to Help->Eclipse Marketplace
Type JST extension in search box.
Install JSP Adapters for Luna
Restart the eclispe
You should be able to see Tocmat 8 server while adding new server.
In addition to #Jason's answer I had to do a bit more to get my app to run.
Download & unzip Eclipse IDE for Java EE Developers (Note the EE edition)
Download & unzip Eclipse's Web Tools Platform Stable (Milestone) 3.6+
Overwrite the two folders in the Eclipse IDE, with the WTP folder(s) (features & plugins folders)
Download and unzip Tomcat 8
In eclipse new -> other -> server -> Tomcat 8 (choose the unzipped location)
If you get a 404, click the Tomcat 8 in the Servers view -> Server Locations -> Change to Use Tomcat installation, and change the Deploy path: to webapps *
(If you can't edit this, delete any published webapps)
To add the Tomcat 9.0 (Tomcat build from the trunk) as a server in Eclipse.
Update the ServerInfo.properties file properties as below.
server.info=Apache Tomcat/#VERSION#
server.number=#VERSION_NUMBER#
server.built=#VERSION_BUILT#
server.info=Apache Tomcat/7.0.57
server.number=7.0.57.0
server.built=Nov 3 2014 08:39:16 UTC
Build the tomcat server from trunk and add the server as tomcat7 instance in Eclipse.
ServerInfo.properties file location : \tomcat\java\org\apache\catalina\util\ServerInfo.properties
The latest version of Springsource STS (3.6) supports Tomcat 8. It is based on eclipse Luna 4.4 and supports Java 8. Have at it!
Alternatively we can use eclipse update site (Help -> Install New Features -> Add Site (urls below) -> Select desired Features).
For Luna: http://download.eclipse.org/webtools/repository/luna
For Kepler: http://download.eclipse.org/webtools/repository/kepler
For Helios: http://download.eclipse.org/webtools/repository/helios
For older version: http://download.eclipse.org/webtools/updates/
Downloaded Eclipse Luna and installed WTP using http://download.eclipse.org/webtools/repository/luna
Downloaded Tomcat 8 and configured new server in Eclipse. I am able to setup tomcat 8 now in Eclipse luna
If you have untarred your own version of tomcat v8 with a root user into a custom directory (linux) then the default permissions on the TOMCATROOT/lib directory do not allow normal user access.
Eclipse will not be able to see the catalina.jar to check the version. So no amount of fiddling aorund with the server.properties will help!
just add chmod u+x lib/ to allow normal user access to the libs.
I am currently working with a product that is built onto Eclipse version 3.4.2.
I am trying to install the jaxb builder plugin, but it is not working.
So far I have tried:
Unzipping the folder into the Eclipse plugins folder and then restarting Eclipse
The restarting Eclipse using the -clean flag
Unzipping the folder into the product's (built onto Eclipse) plugin folder and then restarting with and without -clean
Unzipping the folder into the dropins folder and then restarting Eclipse
I think that it may be possible that this version of jaxb builder doesn't support my version of Eclipse, but I can't figure out how to find that information. I tried emailing the address on the "Contact Us" page, but it came right back to me.
Is it possible that the product has been discontinued? How can I find out?
Discontinued? I don't know but the last build is from 2011-05. It's built against Eclipse 3.4 (see plugin.xml). What do you mean be "not working"? Exceptions? Entries in Eclipse error log/view?
Turns out it was the application's fault. I'm not exactly sure what the problem was, but when I did the exact same thing in a regular Eclipse environment, it came up with no issues.
I will edit if I get more information.
I'm struggling to get the Eclipse FindBugs plugin to work and am sure there's a schoolboy error being made somewhere.
I extracted the file findbugs-2.0.2-rc2.zip to a local folder C:\Program Files\findbugs-2.0.2-rc2 and running findbugs.bat, FindBugs works fine running it over a local Java (Eclipse) project.
I added the FindBugs update site, it found "FindBugs Feature, 2.0.1.20120712" and installed it. Restarting, right-clicking on an open Java Project doesn't display the "FindBugs" option (that this video shows).
I looked in Window > Preferences to try to find a way to inform the plugin of the local FindBugs installation (in Program Files), but couldn't find anything.
Uninstalling "FindBug Feature", I tried extracting the FindBugs Eclipse plugin zip file into Eclipse's plugins folder, but after a restart, saw no difference.
Help > About Eclipse > Installation Details > Installed Software lists "FindBugs Feature 2.0.1.20120712".
Can anyone please offer a pointer on where I'm going wrong here? Thanks!
Windows 7, Eclipse IDE for Java EE Developers Juno SR1, JDK 1.7.0_09, FindBugs 2.0.2-rc2
As suggested above, problem is likely caused by not having appropriate write access to the C:\Program Files\Eclipse\plugins folder.
Solution:
Close Eclipse. Restart Eclipse as Administrator (right click - Run as Administrator). Reinstall plugin. Restart Eclipse.
It looks like the Findbugs plugin wasn't installed properly and/or disabled by Eclipse. There can be several causes.
Multiple versions of the same plugin. To make sure this isn't the case, remove all Findbugs versions (installed manually and via the marketplace), and reinstall one (preferably via the marketplace). Watch for any warnings during installation.
There is a (dependency) conflict with another plugin. However, if this is the case I think Eclipse will warn in the log which other plugin is the cause of the conflict.
Rights problem. Make sure you have write permissions in the main Eclipse folder and all it's child folders.
I remember reading somewhere that installing Eclipse under the C:\Program Files\ in Windows can also be causing problems. Try moving Eclipse to a different folder, e.g. C:\Eclipse
Hi I also faced the similar problem but from my own experience i can suggest you the solution :-
Plz ensure that you are using eclipse version 3.6 or higher. findbugs 2.0 is not compatible with Eclipse 3.5(Eclipse Galileo).
1) Plz extract the findbugs zip file into eclipse folder(wher your eclipse is installed). This will automatically move findbug plugins into eclipse plugins folder. Restart the eclipse and you will find findbugs option on right clicking on project.
2) if 1 step does not work plz remove all the findbug jars for the eclipse plugins folder and place the complete folder into the eclipse dropins folder. Restart the eclipse and you will see the difference.
You can follow these step's to make findbugs work in your eclipse.
1.Install FireBug plugin from marketplace.
Help->Eclipse Marketplace ->then search for FindBugs
2.Configure FindBug for your project
using Maven Without Maven
This worked fine for me using eclipse juno.
i'm running into following errors everytime i start eclipse. If i move my project to a new workspace, everything works fine for the duration of one session - as soon as i open eclipse for the next time, the same thing is popping up again.
I tried various suggestions i found in other posts (closing/reopening project, validation, cleaning,etc.) without success. Here is my stacktrace from the last session (its too long to post it directly in here:))
The main symptom is that Tomcat doesnt start - it is stuck at 7%.
Thank you guys in advance, your help is highly appreciated!! If you need anything else, just leave me a comment and i i'll post it!
Your Eclipse environment is seriously messed up. Perhaps you installed plugins the wrong way or you used the wrong Eclipse or plugin version.
Trash everything. Delete the Eclipse program folder altogether. You can keep your workspace folder, but you should delete its .metadata folder. Now download a fresh copy of Eclipse for Java EE (note, with the EE!), extract it and then integrate Tomcat again the usual way by the Servers view. Note that you don't need any additional plugins for this step.
JBoss Tools should be installed via Help > Install New Software. You should specify the JBoss Tools update site matching the exact Eclipse version. Currently it's Indigo SR2, so you should specify http://download.jboss.org/jbosstools/updates/indigo/SR2/ as URL.
Please take a look here:
alt text http://img16.imageshack.us/img16/2810/errrp.jpg
Why i got that error when i'm trying to update my Eclipse Galileo to the newest Eclipse M6 Helios?
I'm using the update URL from here:
http://eclipsesource.com/blogs/2010/03/14/eclipse-3-6-m6-helios-available-for-download/
Is this a bug? If not, what can i do?
Please help. Thanks!
Can you try the upgrade process after re-launching eclipse with the -clean option?
Do you confirm you are using the http://download.eclipse.org/eclipse/updates/3.6milestones/ update site address?
What version of eclipse are you using (3.5, 3.5.1, 3.5.2?) and what extra plugin did you installed?
For instance, if you have installed Scala for Eclipse, you could not upgrade AspectJ which could block the upgrade process. (see this thread for illustration)
To summarize the 3-days span and 15 comments below:
An easiest path to solve this would be:
have a fresh installation of Eclipse, especially the Java EE Helios package (see Helios packages)
with an eclipse.ini including a -data /path/to/existing workspace
( That way, you have 2 Eclipse referencing the same Eclipse projects. You can launch one or the other, and if the new one does not work, you can still revert to the old one. This is safer than trying modifying extensively -- through the update process -- your current Eclipse)
add the GlassFish plugin for Eclipse
(download both the plugin and feature jar files, quit Eclipse, then copy the unzipped contents of the first into the plugins directory and the second into the features directory of your Eclipse installation)
Check you Java EE JDK if needed
And here you go: you should be able to see a GlassFish Server and integrate it as a target runtime there.