]
Rob Stryker updated JBIDE-18130:
--------------------------------
Affects Version/s: 4.2.0.CR1
JBDS doesn't follow/honor <module-alias> of jboss modules
---------------------------------------------------------
Key: JBIDE-18130
URL:
https://issues.jboss.org/browse/JBIDE-18130
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.2.0.CR1
Reporter: Takayuki Konishi
Assignee: Rob Stryker
Fix For: 4.2.0.CR1
Attachments: modalias.zip
JBDS 8 beta3 cannot resolve <module-alias> of jboss modules. For example,
org.apache.log4j cannot resolved with these configurations [1][2][3]. They are valid; when
I create a similar maven project, it can be deployed in EAP 6.3.0.
[1]
{code:title=MANIFEST.MF|borderStyle=solid}
Manifest-Version: 1.0
Class-Path:
Dependencies: org.apache.log4j
{code}
[2]
{code}
import org.apache.log4j.Logger;
...
public class SampleClass{
private static final Logger logger = Logger.getLogger(SampleClass.class);
...
{code}
[3]
{code:title=module.xml|borderStyle=solid}
<module-alias xmlns="urn:jboss:module:1.1" name="org.apache.log4j"
target-name="org.jboss.log4j.logmanager"/>
{code}