When using a hint to add the embeddable EJB container to the project, the IDE will add the version from GF 3.0. See class o.n.m.maven.j2ee.ejb.EjbTestOutputObserver in module maven.j2ee. Instead, the IDE should use the embeddable container for the server that is set as the target server for the project (this will be important when more servers support Java EE 6).
For 6.9.1, we should at least update the container to GF 3.0.1.
I tried to update the container to GF 3.0.1, and encountered the following problem: https://glassfish.dev.java.net/issues/show_bug.cgi?id=12278
Also, removing 6.9.1_CANDIDATE, this is probably not worth it.
Perhaps HTML editor issue?
(In reply to comment #2)
> Perhaps HTML editor issue?
Disregard - it is different issue.
See issue 190670 - system scope must be used instead of provided.
*** Bug 191209 has been marked as a duplicate of this bug. ***
When issue 191590 is addressed, we should remove the current UI (hint on the Maven project), so this bug will become obsolete.
While fixing issue 191590 I removed output listener do this issue is obsolete now.
Actually, this is still relevant - the new code in EmbeddableEJBContainerHint still hardcodes a GlassFish-specific POM URL. So for JBoss, you are out of luck. The idea of this issue is to acquire the relevant URL from the server plugin, rather than hardcoding it for GlassFish in the server-independent code.
It is true that we may need a j2eeserver API enhancement for this - for Ant projects, we are using getToolClasspathEntries(TOOL_EMBEDDABLE_EJB) to acquire the classpath, but for Maven this is not usable.
But feel free to treat this as an enhancement rather than a defect.
EmbeddableEJBContainerHint handles at the moment only GlassFish servers - version 3 and 3.1. Mainly because GF has very specific way how it deals with Embeddable EJB server. Once there is a JBoss with embeddable EJB server we will have to implement support for it based on how JBoss works.
EmbeddableEJBContainerHint uses ServerPlugins API (ie. getToolClasspathEntries(TOOL_EMBEDDABLE_EJB)) to retrieve location of JAR to add to pom.xml. But despite adding this JAR to pom.xml it needs an artifact name and version to add to pom.xml even if they are never used in practice. And these are hardcoded.
Overall I think this issue is resolved and new issue should be filled for JBoss once it is available.
Unit testing on JBoss is filed as a separate issue 191554.