maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Gurevich (JIRA)" <>
Subject [jira] (MEAR-146) Expose parameter to not write library-directory element in application.xml
Date Thu, 02 Aug 2012 22:31:21 GMT


Sean Gurevich commented on MEAR-146:

That would work and be clear. BTW, I mentioned this side-effect to an Architect at Oracle
during a sales meeting. She said that she would pass along the issue to the team. I have not
heard back or seen a new version of WebLogic, yet. Thanks for providing a workaround!
> Expose parameter to not write library-directory element in application.xml
> --------------------------------------------------------------------------
>                 Key: MEAR-146
>                 URL:
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.7
>         Environment: Oracle WebLogic
>            Reporter: Alex Halovanic
>            Priority: Minor
>         Attachments: ear-remove-librarydirectory-IT.patch, ear-remove-librarydirectory.patch
> The current handling of defaultLibBundleDir leads to some issues on Oracle Weblogic 10+.
 The Ear plugin currently sets library-directory to the value of defaultLibBundleDir in the
application.xml for EARs v5+.  Some of Oracle's classloading features break (specifically
"Generic File Loading") when this element is set.  defaultLibBundleDir has to be set to APP-INF/lib
since this is the magic library folder for WebLogic.
> The patch adds a parameter to prevent setting library-directory for cases like this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message