Noticing these lines from JBIDE-5916:

"However even after I do this, I notice in my Package Explorer that there is NO classpath container containing any ESB jars on hte project. So I check the .classpath file ot see if ANYTHING was added at all, and I see this:

<classpathentry kind="con" path="server.supplied/SomeName"/>

Aside from the ridiculously short and uninformative name "server.supplied", the adept user will note that this entry was not, actually, server supplied at all, but rather the other option, as I outlined abouve and pointed directly to an esb installation. Aside from that, this "server.supplied" is directly visible in the Java Build Path property page, under the Libraries tab. Which means this constant is exposed to users to see."

AFAIK we added support in JBoss AS to return esb jar's when asked to supply that for esb facets. This seem to not be used at all, but instead it is inserting broken server.supplied entry into the classpath where it should actually be asking the server via the facet mechanism to provide it when the JBoss Runtime is added to the project!

I'm marking this as blocker sine I hope this is a trivial fix so we can just use the standard mechanism and at least get rid of that broken server.supplied entry.

If not, well lets discuss options.