Bug 296899 - When add a server runtime environment for JBOSS AS without "default" server,works not correctly.
Summary: When add a server runtime environment for JBOSS AS without "default" server,w...
Status: VERIFIED NOT_ECLIPSE
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.6   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.6 M4   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-04 03:37 EST by jia.hongchao CLA
Modified: 2009-12-08 04:34 EST (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 jia.hongchao CLA 2009-12-04 03:37:14 EST
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_2; zh-cn) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10
Build Identifier: 20090621-0832

I had JBOSS 4.2.3 installed ,I removed the "default" directory under "server" folder,but I have "dev-core"and"dev-www"instances. When I add server runtime environment,It says "Missing classpath entry /Applications/jboss-4.2.3.GA/server/default/lib/mail.jar"

Reproducible: Always

Steps to Reproduce:
1.install JBOSS 4.2.3
2.remove $JBOSS_HOME/server/default
3.add server runtime environment
Comment 1 Frederic Fusier CLA 2009-12-04 05:17:34 EST
This is not an eclipse bug, please report this issue against JBOSS...
Comment 2 Satyam Kandula CLA 2009-12-08 00:32:48 EST
Verified for 3.6M4
Comment 3 jia.hongchao CLA 2009-12-08 01:15:03 EST
what is the meaning if the bug is "VERIFIED"?
I think this is because eclipse assumes every JBOSS has "default" instance, however ,the "default" instance is not required.
Comment 4 Frederic Fusier CLA 2009-12-08 04:34:30 EST
(In reply to comment #3)
> what is the meaning if the bug is "VERIFIED"?
> I think this is because eclipse assumes every JBOSS has "default" instance,
> however ,the "default" instance is not required.

That only means that the verifier agrees that it's not an Eclipse bug, hence there's nothing else we can do about this issue.

Please report this issue to JBOSS, thanks