[ 
https://issues.apache.org/jira/browse/GERONIMO-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Jencks updated GERONIMO-4013:
-----------------------------------

    Attachment: GERONIMO-4013.diff

This patch reverses the changes from GERONIMO-4012 which prevent working on 
this issue, changes the car-maven-plugin, uses the new flag in the gshell-* 
configs, and fixes things up so the build works for me.  I think the gshell-* 
plugins are not getting used in this build but we can look at the dependencies 
added to the plans/geronimo-plugin.xml and see if those are reasonable.

> 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.

Reply via email to