You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Asbach (Jira)" <ji...@apache.org> on 2022/01/12 03:14:00 UTC

[jira] [Created] (MEAR-307) skinny modules war libs are not put into shared lib folder

Benjamin Asbach created MEAR-307:
------------------------------------

             Summary: skinny modules war libs are not put into shared lib folder
                 Key: MEAR-307
                 URL: https://issues.apache.org/jira/browse/MEAR-307
             Project: Maven EAR Plugin
          Issue Type: Bug
    Affects Versions: 3.2.0
            Reporter: Benjamin Asbach
         Attachments: ear-war-skinny-bug-ear.zip

{code:xml}
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-ear-plugin</artifactId>
        <version>3.2.0</version>
        <configuration>
          <version>8</version>
          <defaultLibBundleDir>libs/</defaultLibBundleDir>
          <skinnyModules>true</skinnyModules>
        </configuration>
      </plugin>
    </plugins>
  </build>

  <dependencies>
    <dependency>
      <groupId>org.jenkins-ci.main</groupId>
      <artifactId>jenkins-war</artifactId>
      <version>2.328</version>
      <type>war</type>
    </dependency>
  </dependencies>
{code}

With the current configuration the libs of war application are not placed into libs folder. 

This causes problems when you add an ejb module: The ejb dependencies are placed in libs and the META-INF/MANIFEST-MF classpath entry of the war is set with the libs classpath.

This causes problems with classloading in JBoss EAP.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)