[
https://jira.codehaus.org/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340250#comment-340250
]
Gili commented on MNG-1388:
---------------------------
Defining properties fails to solve the problem because transitive dependencies
can and do span across multiple organizations. Meaning,
Company A publishes libraries A1, A2, A3 which depend on libraries B1, B2, B3
written by company B, which depend on libraries C1, C2, C3 written by company
C. Defining properties this way leaks information from the innermost dependency
to the outermost one, meaning:
# Anyone building a native library needs to also know how to build all their
transitive dependencies (libraries written by other people). Extrapolate this
across a couple more level and this gets very complicated very fast.
# This approach requires property names to be unique across the entire build
tree, but again we don't own all transitive dependencies (this spans multiple
organizations).
This issue should be reopened.
> Transitive Dependencies in a profile are not used
> -------------------------------------------------
>
> Key: MNG-1388
> URL: https://jira.codehaus.org/browse/MNG-1388
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0
> Environment: Windows XP using Maven 2.0.
> Reporter: Damian Bradicich
> Fix For: Issues to be reviewed for 3.x
>
>
> I have a jar project file that defines a dependency inside a certain profile.
> If I then include that project inside of another war project, the
> dependencies defined in the jar project's profile isn't getting transferred
> over to the war.
> Ie we have this:
> A depends on SQL or Oracle depending on profile
> B depends on A.
> If sql profile is active, I would expect that when I build B, it pulls
> the transitive dependancy on sql from A.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
