[ https://issues.apache.org/jira/browse/MEAR-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marat Abrarov updated MEAR-307: ------------------------------- Attachment: MEAR-307_fixed_example.zip > 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 > Priority: Major > Attachments: MEAR-307_fixed_example.zip, 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)