You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "franck bonin (JIRA)" <ji...@apache.org> on 2016/01/27 10:25:39 UTC

[jira] [Updated] (SCM-816) Can't bootstrap or checkout project with child module

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

franck bonin updated SCM-816:
-----------------------------
    Description: 
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}}

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


> Can't bootstrap or checkout project with child module
> -----------------------------------------------------
>
>                 Key: SCM-816
>                 URL: https://issues.apache.org/jira/browse/SCM-816
>             Project: Maven SCM
>          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
>
> 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
(v6.3.4#6332)