You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Stephane Nicoll (JIRA)" <ji...@codehaus.org> on 2006/11/06 09:43:31 UTC

[jira] Commented: (MEAR-46) Java modules do not work

    [ http://jira.codehaus.org/browse/MEAR-46?page=comments#action_79372 ] 
            
Stephane Nicoll commented on MEAR-46:
-------------------------------------

Your patch makes no sense. Those are 3rd party libs, not ejb-clients

NOTE: ejb-clients have their own type "ejb-client". So nothing is broken. If you have an ejb-client artifact, name it properly.



> Java modules do not work
> ------------------------
>
>                 Key: MEAR-46
>                 URL: http://jira.codehaus.org/browse/MEAR-46
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1, 2.2, 2.0
>            Reporter: David Blevins
>         Attachments: corrected-tests.patch
>
>
> EJB clients are specified in an application.xml via 
> <module><java>pathTo.jar</java></module>
> However the tests that use the "javaModule" element, do not generate the above entry as they should.  In general the support for this is broken.  Any jar with a "META-INF/application-client.xml" file should be added to the application.xml unless it is explicitly excluded via a <javaModule> entry with the <exclude>true</exclude> tag.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira