[ 
https://issues.apache.org/jira/browse/SCM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963278#comment-17963278
 ] 

ASF GitHub Bot commented on SCM-816:
------------------------------------

jira-importer commented on issue #1046:
URL: https://github.com/apache/maven-scm/issues/1046#issuecomment-2964642685

   **[Robert 
Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)**
 commented
   
   When you call a phase or goal, Maven will first analyze the project 
structure. In your case: you have the root pom of a multimodule project, but 
the modules are missing, hence the exception. With `-N` you tell Maven to only 
execute the phase or goal on the current pom.xml. So Maven has no need to 
analyze the project structure and can execute it.
   So I'd say it is the right usage. There's no other way to solve this.
   I'll keep it open for documentation
   




> Can't bootstrap or checkout project with child module
> -----------------------------------------------------
>
>                 Key: SCM-816
>                 URL: https://issues.apache.org/jira/browse/SCM-816
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-plugin
>    Affects Versions: 1.9.4
>         Environment: Apache Maven 3.2.5 
> (NON-CANONICAL_2015-04-01T06:42:27_mockbuild; 2015-04-01T08:42:27+02:00)
> Maven home: /usr/share/maven
> Java version: 1.8.0_65, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.fc22.x86_64/jre
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "linux", version: "4.2.6-200.fc22.x86_64", arch: "amd64", family: 
> "unix"
>            Reporter: franck bonin
>            Assignee: Robert Scholte
>            Priority: Major
>             Fix For: 1.9.5
>
>
> I don't know if it's a maven or a scm plugin issue.
> But, when we try to bootstrap or checkout a project using its single pom 
> description, Maven fail complaining about missing child modules. Which is 
> annoying since retrieving child modules is just why we try to boostrap the 
> project...
> steps to reproduce :
> 1- lets say we get a pom file from nexus :
> {{mvn dependency:copy -Dartifact=my.organisation:sample-pack:1.0.0.0:pom 
> -DoutputDirectory=.}}
>  The retrieved pom file contains scm information and some sub-modules 
> declaration
> 2- try to scm:bootstrap or scm:checkout it with maven :
> {{mvn scm:bootstrap -Dusername=<username> -Dpassword=<password> -f 
> sample-pack-1.0.0.0.pom}}
> fail with maven error : 
> [ERROR]     Child module /path/to/some/where/./moduleb of 
> /path/to/some/where/sample-pack-1.0.0.0.pom does not exist
> [ERROR]     Child module /path/to/some/where/./sample of 
> /path/to/some/where/sample-pack-1.0.0.0.pom does not exist
> [ERROR]     Child module /path/to/some/where/./modulea of 
> /path/to/some/where/sample-pack-1.0.0.0.pom does not exist



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to