[
https://issues.apache.org/jira/browse/GERONIMO-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597053#action_12597053
]
David Jencks commented on GERONIMO-4013:
----------------------------------------
Time will tell but I think rev 656537 fixes this issue. We now construct our
own tree modeling the dependencies and remove the ones as direct dependencies
that are also available from ancestor cars. The DependencyTree maven builds
won't work since it eliminates lots of duplicates, typically removing the ones
farther from the starting project, those often being the ones in a car file
that we want to rely on.
> Make our dependency usage the same as maven dependency usage via
> car-maven-plugin
> ---------------------------------------------------------------------------------
>
> Key: GERONIMO-4013
> URL: https://issues.apache.org/jira/browse/GERONIMO-4013
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 2.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: GERONIMO-4013.diff
>
>
> Right now the car-maven-plugin ignores maven transitive dependencies. One
> reason for this is that our build is not using our plugins as the
> "classloader source" of the maven dependencies that are in the plugin poms.
> If we restructured our build so that the pom dependency graph matched the
> geronimo classloader graph then perhaps we could let the car-maven-plugin
> follow transitive dependencies, thus making our view of dependencies pretty
> much the same as maven's.
> This may show up many other problems, such as too many badly scoped
> dependencies in all sorts of projects we use.
> One first step is to try out the car-maven-plugin with a flag for following
> transitive dependencies. As long as it is false we ought to get pretty much
> the previous behavior.
> A first use could be for the new gshell plugins so they don't have to restate
> all the transitive dependencies. This may show up scope problems as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
