[
https://issues.apache.org/jira/browse/MEAR-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474463#comment-17474463
]
Benjamin Asbach edited comment on MEAR-307 at 1/12/22, 1:16 PM:
----------------------------------------------------------------
[~abrarovm], thansk for your fast response. I wonder if this is a technical
limitation?
I'd expect that the war should behave somehow similar to other modules where I
don't need to define the dependencies manually.
-For my use case (1war + 2ejb) I also end up with doubled dependencies: Some
war dependencies are present in libs and in war/WEB-INF/lib.-
was (Author: asbachb):
[~abrarovm], thansk for your fast response. I wonder if this is a technical
limitation?
I'd expect that the war should behave somehow similar to other modules where I
don't need to define the dependencies manually.
For my use case (1war + 2ejb) I also end up with doubled dependencies: Some
war dependencies are present in libs and in war/WEB-INF/lib.
> skinny modules war libs are not put into shared lib directory
> -------------------------------------------------------------
>
> 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 directory.
> 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)
