[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-8437) Jar files wrongly classified als deployable modules

[Max Rydahl Andersen (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-8437:
---------------------------------------

    Fix Version/s: 3.3.0.M2
                       (was: 3.3.0.M1)


> Jar files wrongly classified als deployable modules
> ---------------------------------------------------
>
>                 Key: JBIDE-8437
>                 URL: https://issues.jboss.org/browse/JBIDE-8437
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS, UpStream
>    Affects Versions: 3.2.0.CR1
>            Reporter: arjan tijms
>            Assignee: Rob Stryker
>              Labels: deployment, jar, module
>             Fix For: 3.3.0.M2
>
>
> When the library folder of an EAR (/lib) or WEB module (/WEB-INF/lib) contains jar files that have a Main-Class entry in their manifest file, Jboss tools designates them as "J2EE Application Client Module".
> This is visible in the GUI in the Servers view when unfolding a runtime server. The above mentioned jar files from EAR/lib are listed between the normal EJB and WEB modules. When you unfold a WEB module in this view, the above mentioned jar files from /WEB-INF/lib are listed here.
> The problem is also visible in the server log. For each jar file being present in EAR/lib and WEB-INF/lib with the mentioned Main-Class entry, a message is printed:
> "Module [name of jar file] published without error."
> Additionally, if a jar file in EAR/lib has classes with EJB annotations, a similar thing happens as with jar files that have a Main-Class entry. The only difference is that in this case the jar file in question is being branded as "J2EE EJB Module"

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira