Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352778 - Can't create server for Jetty 7.4 using server adapter on Indigo
Summary: Can't create server for Jetty 7.4 using server adapter on Indigo
Status: CLOSED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: wtp (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 7.5.x   Edit
Assignee: Jesse McConnell CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-21 11:48 EDT by Missing name CLA
Modified: 2011-07-27 07:48 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Missing name CLA 2011-07-21 11:48:33 EDT
Build Identifier: 20110615-0604

I installed the WTP plugin as per the instructions listed here:

http://wiki.eclipse.org/Jetty_WTP_Plugin/Jetty_WTP_Install

When I go create my server and expand the Jetty list I can see listed 7.1, 7.2, 7.3, 7.4 and 8.0 but 7.3 and 7.4 icons are red.

When I pick 7.4 and click next it automatically asks me to add project resources to the server instead of asking me to pick my jetty distribution folder.

So I picked 7.2 instead, clicked next and pointed to my 7.4 folder. It seems to work is that ok?

Red icons:
http://imageshack.us/photo/my-images/26/jetty2v.jpg/

Picked 7.2 and pointed to 7.4 folder
http://imageshack.us/photo/my-images/713/jetty1.jpg/

Thanks

Reproducible: Always

Steps to Reproduce:
Using fresh install of Eclipse indigo, new workspace everything fresh.

1. Create new server in Eclipse: File -> New -> Other -> Server
2. Look at Jetty options
Comment 1 Jesse McConnell CLA 2011-07-21 15:38:21 EDT
I just pushed an update with this fix in it

also updated from 7.4.3 to 7.4.4 as well

please hit the update site to get the latest copy of the plugin

1.0.0.201107211531

cheers,
Comment 2 Daniel Plasto CLA 2011-07-27 07:48:39 EDT
I encountered the same problem in the apparently fixed version: 1.0.0.201107211531.

Upgrading to the latest development build has resolved this for me though: 1.0.0.201107261728