Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
My large, multi-module Maven project validation (Maven Enforcer plug-in) is playing tricks on me. moduleA> mvn validate correctly finds all modules runs enforcer on all of them displays co...
#1: Initial revision
by
LAFK
·
2023-06-26T06:39:16Z (over 1 year ago)
Running mvn validate does not show rules passed message though it should
My large, multi-module Maven project validation (Maven Enforcer plug-in) is playing tricks on me. `moduleA> mvn validate` - correctly finds all modules - runs enforcer on all of them - displays consistent output in all 7 runs I did so far - enforcer "rules passed" message appears in 5/7 modules - **2 modules never output that message** - all modules are reported as successes, including these 2 - if I ran `mvn validate` on these modules directly (`cd moduleDir; mvn validate` or `mvn validate -f moduleDir/pom.xml` the output is there) - effective POMs show that configuration of enforcer is fine, identical on all modules in fact What I want to see: > [INFO] --- enforcer:3.3.0:enforce (enforce-maven) @ moduleNameHere --- > [INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion passed > [INFO] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion passed What I see instead, on 2 "faulty" modules is only this: > [INFO] --- enforcer:3.3.0:enforce (enforce-maven) @ moduleNameHere --- My question: **do I have a problem or not**? Should I worry that the output for those two modules differ?