Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Comments on Running mvn validate does not show rules passed message though it should

Post

Running mvn validate does not show rules passed message though it should

+3
−0

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?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Just to be sure, it's the same two modules that are consistency missing? Are you able to see what hap... (2 comments)
Just to be sure, it's the same two modules that are consistency missing? Are you able to see what hap...
Mark‭ wrote over 1 year ago

Just to be sure, it's the same two modules that are consistency missing? Are you able to see what happens if you temporarily disable a few other modules? Are the problematic modules dependend/nested different to the other modules? This may sound incredibly wild, but have you tried another terminal or piping output to file to see if the behavior persists?

Since you've checked the enforcer config in the effective POM and ran the modules individually, I personally wouldn't worry much about it.

LAFK‭ wrote over 1 year ago

Neato. Will try tomorrow, when I'll have access to that machine, my thanks for the ideas.