Artifacts should be copied by user selection (runtime, compile, etc) about onejar-maven-plugin

[GoogleCodeExporter]

This is a classic problem with artifacts which are not declared correctly, 
bringing in too many or too few transitive dependencies. It should be handled 
by the authors/maintainers of those dependencies, but can be overridden by you 
in the <dependency> declaration using <excludes>.

Original comment by [email protected] on 6 Oct 2010 at 8:48

• Changed state: WontFix
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I know how to declare dependencies and their transitive behavior and I'm quite 
sure I've not made a mistake.  Compile scoped transitive dependencies should 
not be copied into the one-jar archive but they are.

Related to this bug: one-jar also copies <optional>true</optional> transitive 
dependencies into the archive.

Original comment by [email protected] on 6 Oct 2010 at 9:08

[GoogleCodeExporter]

My mistake; I was too quick to dismiss. Thanks for clarifying!

Original comment by [email protected] on 7 Oct 2010 at 3:55

• Changed state: Accepted
• Added labels: Type-Defect
• Removed labels: Type-Enhancement

[GoogleCodeExporter]

This declaration in my parent pom:

            <dependency>
                <groupId>javax.inject</groupId>
                <artifactId>javax.inject</artifactId>
                <version>${javax.inject.version}</version>
                <scope>compile</scope>
                <optional>true</optional>
            </dependency>

Results in the javax.inject jar inside my one-jar archive.  Why?

Original comment by [email protected] on 18 Nov 2011 at 6:13