You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/10/11 10:15:53 UTC
[GitHub] [maven-mvnd] ppalaga commented on issue #492: Provide a mechanism to exclude building specific modules in parallel
ppalaga commented on issue #492:
URL: https://github.com/apache/maven-mvnd/issues/492#issuecomment-1274459704
Yes, adding
```
<dependency>
<groupId>org.my-group</groupId>
<artifactId>B</artifactId>
<version>${project.version}</version>
<type>pom</type>
<scope>test</scope>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
```
to `C` would make `C` always start building after `B` is fully built.
It is true that this not really easy to maintain for the cases where the execution order actually does not matter.
For the tests use case, maybe the locking would suffice on the level of mojos rather than the whole modules?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org