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

Stephane Nicoll commented on MEAR-146:
--------------------------------------

In that case, I prefer a weblogic configuration option, like we've done for 
JBoss. Your patch is a too wide option that sole purpose is to workaround a bug.

Something like

{code:xml}
<configuration>
  <weblogic>
    <write-library-directory>false</write-library-directory>
  </weblogic>
</configuration>
{code}


                
> 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.8
>         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: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to