maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thilo Tanner (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MNG-3774) Multilevel dependency resolving
Date Tue, 30 Sep 2008 08:25:45 GMT

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

Thilo Tanner closed MNG-3774.
-----------------------------

    Resolution: Not A Bug

The problem was a misuse of the assembly plugin. Using the attached goal instead of assembly
solved the problem.

> Multilevel dependency resolving
> -------------------------------
>
>                 Key: MNG-3774
>                 URL: http://jira.codehaus.org/browse/MNG-3774
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0.8, 2.0.9, 2.1.0-M1
>         Environment: Ubuntu Linux
>            Reporter: Thilo Tanner
>
> We created a multilevel Maven project
> - Project-Pom (Packaging: pom)
>   - 1. Module (Packaging: jar)
>   - 2. Module (Packaging: pom)
>     - 2.1. Module (Packaging: jar)
>     - 2.2. Module (Packaging: jar)
>     - 2.3. Module (Packaging: war)
> Module 2.2. is a dependency of module 2.3. Everything works fine when I build Module
2 alone (all artifacts getting installed to local repo). But when I build the whole project,
just module 1 get installed and then the build fails because dependency 2.2. is missing in
module 2.3. (because no artifacts of module 2 were installed to local repo) when the multilevel
pom is built. All subprojects works fine when they are built alone.

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

        

Mime
View raw message