Hi Stephen,
The organizational pom can prescribe the use of the most recently
released ruleset.
The next version of the ruleset would "technically" be checked against
the previous version, but as rulesets are not java code the check will
not be applied on that artifact.
True.
But its a little bit tricky to get this setup off the ground in the
first place:
1. Release version 1.0 of organizational POM
(without m-pmd-p)
2. Release version 1.0 of ruleset
(inheriting from organizational POM, version 1.0)
3. Release version 2.0 of organizational POM
(with m-pmd-p and ruleset, version 1.0)
And the ruleset is doomed to perpetually lag behind one version of the
organizational POM.
I think I like the two-parents solution better: the organizational POM
is restricted to (plugin|dependency)Management, with the other parent
binding plugins for real.
Best wishes,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
