Maven 2.x JBoss Packaging Plugin

Dependency scope not respected

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: 2.0-beta-1
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

When you create a SAR using jboss-packaging-maven-plugin with dependencies:
A (runtime) -> B
C (provided) -> B
with A, B, C artifacts and where '->' means transitive dependency,

then B should not be packaged under lib/ within the SAR.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Paul Gier added a comment -

If A is a runtime dependency, then I believe you would want the dependency included in the sar. If the dependency is set to a "provided" scope, the dependeny (direct or transitive) is not included in the sar. At least this is how it's working in the current snapshot.

I will mark this as won't fix unless some more detail can be provided.

Show
Paul Gier added a comment - If A is a runtime dependency, then I believe you would want the dependency included in the sar. If the dependency is set to a "provided" scope, the dependeny (direct or transitive) is not included in the sar. At least this is how it's working in the current snapshot. I will mark this as won't fix unless some more detail can be provided.
Hide
Permalink
Paul Gier added a comment -

I'm going to close this issue because I believe the current behaviour is correct. Please re-open and clarify if this is still a problem for you.

Show
Paul Gier added a comment - I'm going to close this issue because I believe the current behaviour is correct. Please re-open and clarify if this is still a problem for you.

People

  • Assignee:
    Paul Gier
    Reporter:
    Frank Cornelis
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: