maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MNGSITE-126) [Documentation] Reactor sorting
Date Sun, 06 Sep 2015 20:44:52 GMT

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

Michael Osipov closed MNGSITE-126.
----------------------------------
    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.

> [Documentation] Reactor sorting
> -------------------------------
>
>                 Key: MNGSITE-126
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-126
>             Project: Maven Project Web Site
>          Issue Type: Improvement
>            Reporter: Andrey Vorobiev
>
> Guide to Working with Multiple Modules (http://maven.apache.org/guides/mini/guide-multiple-modules.html)
says:
> >> The following relationships are honoured when sorting projects:
> >> a project dependency on another module in the build
> >> a plugin declaration where the plugin is another modules in the build
> >> a plugin dependency on another module in the build
> >> a build extension declaration on another module in the build
> >> the order declared in the <modules> element (if no other rule applies)
> and what's about parent pom relation?
> For instance we have three modules:
> - parent
> - child-1
> - child-2
> "parent" module is specified as parent pom for modules "child-1" and "child-2":
> <parent>
> ...
>    <artifactId>parent</artifactId>
> ...
> </parent>
> Also we have aggregator module with contents:
> <project>
> ...
>    <modules>
>       <module>path to "parent" module</module>
>       <module>path to "child-1" module</module>
>       <module>path to "child-2" module</module>
>    </modules>
> ...
> </project>
> Next we type: mvn clean install
> Can it be guaranteed that "parent" module will be builded and installed into local repository
before "child-1" and "child-2" modules?
> The same question but in case of multithreaded execution (-T option is provided)?
> As far as I understand from source "maven-core/src/main/java/org/apache/maven/project/ProjectSorter.java"
it can:
> ...
> Parent parent = project.getModel().getParent();
> if ( parent != null )
> {
>    // Parent is added as an edge, but must not cause a cycle - so we remove any other
edges it has
>    // in conflict
>    addEdge( projectMap, vertexMap, null, projectVertex, parent.getGroupId(), parent.getArtifactId(),
>             parent.getVersion(), true, false );
> }
> ...



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

Mime
View raw message