Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Incomplete
-
Affects Version/s: 2.0.1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
When I build a WAR with the following dependencies:
A (scope provided, type pom) -> B (scope compile, type jar)
C (scope runtime, type jar) -> B (scope compile, type jar)
then B gets included under WEB-INF/lib which I think it should not be. I use the provided pom artifact A to represent the dependencies provided by my container.
Issue Links
- is related to
-
MWAR-111
Transitive dependencies of optional dependencies are included in WEB-INF/lib
-
I don't follow. If B has a compiled scope, it should be there.