You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Cailloux (JIRA)" <ji...@apache.org> on 2017/08/17 09:45:00 UTC
[jira] [Created] (MASSEMBLY-869) Spurious dependency when profile
is disabled
Olivier Cailloux created MASSEMBLY-869:
------------------------------------------
Summary: Spurious dependency when profile is disabled
Key: MASSEMBLY-869
URL: https://issues.apache.org/jira/browse/MASSEMBLY-869
Project: Maven Assembly Plugin
Issue Type: Bug
Components: dependencySet
Affects Versions: 3.1.0
Reporter: Olivier Cailloux
Priority: Minor
Attachments: pom.xml, Runnable.xml
My assembly descriptor contains a dependency set entry, that supposedly should include all dependencies for my project and nothing more, namely, only one dependency in my case. But two dependencies get included.
My project uses profiles. The profile configures a “bcprov” property, which determines the (sole) dependency of my project. Under the “swt-unix” profile, this should be org.bouncycastle:bcprov-jdk15on:1.57, while under the “swt-windows” profile, this should be org.bouncycastle:bcprov-jdk14:1.57.
But running {{mvn -P '!swt-unix,swt-windows' package}} includes *both* org.bouncycastle:bcprov-jdk15on:1.57 and org.bouncycastle:bcprov-jdk14:1.57 in the “test-dep-0.0.1-SNAPSHOT-runnable-windows.zip” artifact produced by the assembly.
The problem seems related to the “swt-unix” profile activation section.
Please see [GitHub|https://github.com/oliviercailloux/test-dep] and [Travis|https://travis-ci.org/oliviercailloux/test-dep] to see the issue at work with some debug information (the dependency plugin shows that the correct dependencies seem to have been computed, and the manifest includes the correct classpath entry, yet the dependencies included in the artifact are incorrect).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)