[ 
https://jira.codehaus.org/browse/MEAR-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306316#comment-306316
 ] 

Stéphane Nicoll commented on MEAR-146:
--------------------------------------

no that's no what I meant. Look at MEAR-151. Everything works as of now but the 
only difference is that we add an option to generate an empty library-directory 
element. 

I am talking about a *separate* option. If that works, then we can meet both 
requests with a single option (yours and MEAR-151). And I also think that "do 
not write library-directory", "write empty library-directory" and "write 
library directory with defaultLibBundleDir value" are too many options. It will 
be confusing.

Thanks
                
> Expose parameter to not write library-directory element in application.xml
> --------------------------------------------------------------------------
>
>                 Key: MEAR-146
>                 URL: https://jira.codehaus.org/browse/MEAR-146
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.7
>         Environment: Oracle WebLogic
>            Reporter: Alex Halovanic
>            Priority: Minor
>             Fix For: 2.8
>
>         Attachments: ear-remove-librarydirectory-IT.patch, 
> ear-remove-librarydirectory-IT.patch, ear-remove-librarydirectory.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: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to