[jbosstools-issues] [JBoss JIRA] (JBDS-3124) JBDS doesn't follow/honor <module-alias> of jboss modules
Takayuki Konishi (JIRA)
issues at jboss.org
Tue Aug 26 20:43:59 EDT 2014
[ https://issues.jboss.org/browse/JBDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Takayuki Konishi updated JBDS-3124:
-----------------------------------
Description:
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}
was:
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]
MANIFEST.MF
Manifest-Version: 1.0
Class-Path:
Dependencies: org.apache.log4j
[2]
In a class:
import org.apache.log4j.Logger;
...
public class SampleClass{
private static final Logger logger = Logger.getLogger(SampleClass.class);
...
[3]
module.xml:
<module-alias xmlns="urn:jboss:module:1.1" name="org.apache.log4j" target-name="org.jboss.log4j.logmanager"/>
> JBDS doesn't follow/honor <module-alias> of jboss modules
> ---------------------------------------------------------
>
> Key: JBDS-3124
> URL: https://issues.jboss.org/browse/JBDS-3124
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.0.0.Beta3
> Reporter: Takayuki Konishi
> 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