[
https://issues.apache.org/jira/browse/MNG-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646062#comment-17646062
]
Christoph Läubrich commented on MNG-7623:
-----------------------------------------
One example is I have two modules that both use a mojo and/or library that is
not threadsafe or a resource that can not be shared.
Currently maven warns if one mojo is not marked thread-safe, so maybe it would
also be a valid solution to use that information to determine a project is "not
parallel"....
> Specify if a project can run in parallel
> ----------------------------------------
>
> Key: MNG-7623
> URL: https://issues.apache.org/jira/browse/MNG-7623
> Project: Maven
> Issue Type: Improvement
> Reporter: Christoph Läubrich
> Priority: Major
>
> It would be great if one can specify in the pom if a project is safe to
> execute in parallel.
> I sometimes have a multi-module project where most of the module can run
> easily in parallel but some needs serial execution, currently using some
> "hacks" to enforce this.
> This should work the following way:
> # If all projects are marked as "parallel" all works like today (default)
> # If a project is marked as not run in parallel, first execute all projects
> in the build order until this project
> # Then execute the serial one and proceed with the same (that is execute all
> in parallel until the next serial project is found)
> This could happen on different level, e.g. such a strategy might be delegated
> to the builder, or the code that calling the builder can "slice" the projects
> in the given way and call the builder multiple times.
> Nerveless this will require some change to the project-model to mark a
> project as parallel, or one might be able to use a project-session-property
> or alike.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
