nishaatr opened a new issue, #1521:
URL: https://github.com/apache/maven-release/issues/1521
### Affected version
3.3.1
### Bug description
We run the `maven-release-plugin` strictly to validate that no `-SNAPSHOT`
dependencies remain in our multi-module project:
```bash
./mvnw release:prepare release:clean \
-Darguments="-T1.0C -DskipTests" \
-DautoVersionSubmodules=true \
-DdryRun=true \
-DpushChanges=false
```
We do not observe the thread-safety warning mentioned in
[#1333](https://github.com/apache/maven-release/issues/1333), and this
configuration has run reliably in our project for ~10 months without issue.
Questions for Maintainers
1. Is it safe to use `-T` specifically in dry-run / non-SCM validation
scenarios despite the
[documentation](https://maven.apache.org/maven-release/maven-release-plugin/usage/prepare-release.html)
noting that `release:prepare` is not thread-safe?
2. Is the lack of thread safety tied strictly to stateful SCM operations
(e.g., Git index/locking), or are there hidden reactor/POM race conditions
during a `-DdryRun=true` execution?
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
