[jira] Closed: (MNG-4608) Cross module dependencies for multi-module projects

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-4608.
----------------------------------

    Resolution: Duplicate
      Assignee: Benjamin Bentmann

> Cross module dependencies for multi-module projects
> ---------------------------------------------------
>
>                 Key: MNG-4608
>                 URL: http://jira.codehaus.org/browse/MNG-4608
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>    Affects Versions: 2.0.9
>         Environment: windows, jdk1.6.0_16
>            Reporter: Robert Lieb
>            Assignee: Benjamin Bentmann
>            Priority: Blocker
>
> Considering a multi-module project A which declares two sub-projects (modules) B and C. 
> Having module C indicating in its POM a dependency against module B.
> Module B uses the shade plugin to 'merge' classes from B with his dependencies.
> Separate install of B and C works fine, but an install on A fails by compiling C
> because of missing classes. Maven don't use the generated jar file of B for compiling C.
> I need a different behaviour (maybe command line option) to change it.
> This is not only related to shade plugin. In any cases in which a maven project uses
> some 'manipulation' plugins after compile phase, will fail.

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