[ http://jira.codehaus.org/browse/MEAR-46?page=all ]
David Blevins updated MEAR-46:
------------------------------
Attachment: usage.patch
Fair enough. I personally think it's a bit odd that the default behavior of
the javaModule isn't to create a <module><java> element, but likely most people
don't have j2ee application clients.
I've updated the doc to try and make it more clear that <javaModule> !=
<module><java>. It said something to this affect about jar dependencies and
based on what you've explained that makes perfect sense now, but at the time it
wasn't clear that you were favoring <javaModule> to refer to any dep of type
jar ("java" isn't an artifact type after all so you can see the confusion).
Strictly speaking, even the JavaModule.java is commented as being for j2ee
application clients, but I get the duality of the <javaModule> usage you talk
about.
One last fyi, it seems that the way the code is now even artifacts of type
ejb-client will not be included in the application.xml buy default either.
> 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
> Assigned To: Stephane Nicoll
> Fix For: 2.3
>
> Attachments: corrected-tests.patch, usage.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
