[jbosstools-issues] [JBoss JIRA] (JBIDE-18130) JBDS doesn't follow/honor <module-alias> of jboss modules
Martin Malina (JIRA)
issues at jboss.org
Tue Sep 9 03:59:00 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-18130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Malina closed JBIDE-18130.
---------------------------------
I have verified that this works properly in JBDS 8.0.0.CR1 B225 (I also checked that it does not work in Beta3).
> 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}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jbosstools-issues
mailing list