chore: DevOps mvn install fail early
#324
Conversation
| <artifactId>maven-resources-plugin</artifactId> | ||
| <version>3.3.1</version> | ||
| <groupId>com.github.spotbugs</groupId> | ||
| <artifactId>spotbugs-maven-plugin</artifactId> |
There was a problem hiding this comment.
SpotBugs is last after Jacoco
CharlesDuboisSAP
changed the title
mvn install fail earlymvn install fail early
MatKuhr
left a comment
MatKuhr
left a comment
There was a problem hiding this comment.
This is not suitable when doing PoCs or larger refactorings. There we don't want to fix all PMD and Javadoc requirements just to compile.
Instead, if you want to run all checks fast (i.e. before/without tests), just run mvn install -DskipTests or create an alias for that. Compile takes around 10s (on my machine), so there is no point in moving checks to before that for speed
CheckStyle and PMD still run after compile. |
|
Okay fair, but still it's beneficial to run tests without fixing all javadoc warnings, why not just |
I run tests with IntelliJ, the only time I run |
| <goals> | ||
| <goal>prepare-agent</goal> | ||
| </goals> | ||
| <phase>initialize</phase> |
There was a problem hiding this comment.
It's redundant, the default is already initialize
Context
mvn installshould fail as fast as possible regardless of what step fails.Feature scope: