[
http://jira.codehaus.org/browse/MDEP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107873
]
Cameron Jones commented on MDEP-114:
------------------------------------
The problem i have is that i need to run builds from the parent or the module
and get the same result. In my environment the developers use the full build
from the parent to verify a checkin whereas the build machine builds each
module as a separate task.
The goal i'm trying to achieve is to create a client plugin which contains a
web service stub module and it's required dependencies. Since the client needs
to be as small as possible i need to make sure that only the absolute required
dependencies are included in it's packaging. If run from the parent this is not
the case and the entire project's dependencies are included, even unrelated
modules.
I've managed to work around this by using the assembly plugin instead and
adding a new module for other reasons...in the case of that plugin it looks at
the explicitly defined dependencies on a pom and only includes those. There's
also other options for excluding transitive etc. I think the assembly plugin is
a bit heavy and that the dependency plugin would be the ideal place for this
kind of functionality.
> Copy Dependencies does not have project dependency isolation
> ------------------------------------------------------------
>
> Key: MDEP-114
> URL: http://jira.codehaus.org/browse/MDEP-114
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
> Affects Versions: 2.0-alpha-4
> Reporter: Cameron Jones
> Assignee: Brian Fox
>
> In a multi-module project the copy-dependencies goal gets the list of
> dependencies from the project and not the individual modules. This has the
> effect that if the task is run from a module it has only that module's
> dependencies copied, however if run from the parent the entire project's
> dependencies are copied.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
