[jira] [Closed] (MNG-4660) Use of --resume-from in multi-module project fails with missing inter-module dependencies

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov closed MNG-4660.
-------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Use of --resume-from in multi-module project fails with missing inter-module dependencies
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-4660
>                 URL: https://issues.apache.org/jira/browse/MNG-4660
>             Project: Maven
>          Issue Type: Bug
>          Components: Reactor and workspace
>    Affects Versions: 2.2.1, 3.0-beta-1
>         Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
> Java version: 1.6.0_17
> Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x" version: "10.6.3" arch: "x86_64" Family: "mac"
>            Reporter: Brian Ferris
>            Priority: Major
>         Attachments: modules-parent.tar.gz
>
>
> In a simple multi-module project with a parent pom "modules-parent", two sub modules "module-a" and "module-b", where B depends on A, I've not been able to get the Maven "--resume-from" feature to work.
> Specifically, I expect:
> > mvn --resume-from module-b test
> would resume execution of the "test" goal in "module-b".  Instead it fails with a missing artifact error:
> > [INFO] Failed to resolve artifact.
> > 
> > Missing:
> > ----------
> > 1) org.test:module-a:jar:0.0.1-SNAPSHOT
> Why isn't Maven resolving the within-multi-module dependency?  I've attached a simple project that reproduces the problem with Maven 2.2.1 and Maven 3.0-beta-1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)