Robert Scholte created MNG-6160:
-----------------------------------

             Summary: Forking process not always aware of reactor projects
                 Key: MNG-6160
                 URL: https://issues.apache.org/jira/browse/MNG-6160
             Project: Maven
          Issue Type: Bug
          Components: Reactor and workspace
    Affects Versions: 3.3.9
            Reporter: Robert Scholte
         Attachments: mvn.log

While running {{mvn clean -e -Preporting site}} on the Maven Artifact Resolver 
1.0.3-SNAPSHOT I noticed downloads of files which should be part of the reactor.

{noformat}
[INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[INFO] Forking Maven Artifact Resolver SPI 1.0.3-SNAPSHOT
[INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Downloading: 
https://repository.apache.org/snapshots/org/apache/maven/resolver/maven-resolver-api/1.0.3-SNAPSHOT/maven-resolver-api-1.0.3-20170122.151134-3.pom
Downloaded: 
https://repository.apache.org/snapshots/org/apache/maven/resolver/maven-resolver-api/1.0.3-SNAPSHOT/maven-resolver-api-1.0.3-20170122.151134-3.pom
 (2 KB at 1.6 KB/sec)
{noformat}

There are 2 issues with this: 
- Maven is using other files than the expectd files from the reactor
- In case those files don't exist it'll fail.

See log file for complete evidence



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to