[
https://issues.apache.org/jira/browse/FELIX-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated FELIX-5280:
-----------------------------------
Description:
We have the following situation:
* Maven bundle plugin has version 3.0.1 (or 3.0.0) and contains the
instruction to embed projects with scope=(compile|runtime)
* we have project A having the Maven bundle plugin and following dependency
tree to other projects:
** Project B [scope Compile]
*** Project X [scope Compile]
** Project C [scope Test]
*** Project X [scope Compile]
Expectation:
* when building a jar for the main code, the content of Project X gets
embedded. (No matter whether it is included by test scope additionally to the
scope compile)
Actual:
* As long as there is a transitive dependency to Project X with Test scope,
the project is not embedded.
Other observations:
* Direct dependencies are always included
* if in project C an exclusion to project X would be added, then the jar for
project A would contain X as there are no test dependencies to it
This happens since version 3.0.0 so we have to downgrade the maven plugin
version to 2.5.4 (and thus miss other important features) just to make the
transitive dependency work.
We would be very thankful to know a rough estimation when we can expect an
release that fixes this issue.
was:
We have the following situation:
* Maven bundle plugin has version 3.0.1 (or 3.0.0) and contains the instruction
to embed projects with scope=(compile|runtime)
* we have project A having the Maven bundle plugin and following dependency
tree to other projects:
** Project B [scope Compile]
*** Project X [scope Compile]
** Project C [scope Test]
*** Project X [scope Compile]
Expectation:
* when building a jar for the main code, the content of Project X gets
embedded. (No matter whether it is included by test scope additionally to the
scope compile)
Actual:
* As long as there is a transitive dependency to Project X with Test scope, the
project is not embedded.
Other observations:
* Direct dependencies are always included
* if in project C an exclusion to project X would be added, then the jar for
project A would contain X as there are no test dependencies to it
This happens since version 3.0.0 so we have to downgrade the maven plugin
version to 2.5.4 (and thus miss other important features) just to make the
transitive dependency work.
We would be very thankful to know a rough estimation when we can expect an
release that fixes this issue.
> transitive dependencies get ignored when building jar
> -----------------------------------------------------
>
> Key: FELIX-5280
> URL: https://issues.apache.org/jira/browse/FELIX-5280
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-3.0.0, maven-bundle-plugin-3.0.1
> Environment: Windows 7
> Maven 3.3.3
> JRE ORACLE 1.7.0_45
> Reporter: Michael Krein
> Priority: Critical
> Labels: bug, maven
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> We have the following situation:
> * Maven bundle plugin has version 3.0.1 (or 3.0.0) and contains the
> instruction to embed projects with scope=(compile|runtime)
> * we have project A having the Maven bundle plugin and following dependency
> tree to other projects:
> ** Project B [scope Compile]
> *** Project X [scope Compile]
> ** Project C [scope Test]
> *** Project X [scope Compile]
> Expectation:
> * when building a jar for the main code, the content of Project X gets
> embedded. (No matter whether it is included by test scope additionally to the
> scope compile)
> Actual:
> * As long as there is a transitive dependency to Project X with Test scope,
> the project is not embedded.
> Other observations:
> * Direct dependencies are always included
> * if in project C an exclusion to project X would be added, then the jar for
> project A would contain X as there are no test dependencies to it
> This happens since version 3.0.0 so we have to downgrade the maven plugin
> version to 2.5.4 (and thus miss other important features) just to make the
> transitive dependency work.
> We would be very thankful to know a rough estimation when we can expect an
> release that fixes this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
