[
http://jira.codehaus.org/browse/MENFORCER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166815#action_166815
]
Dan Fabulich commented on MENFORCER-65:
---------------------------------------
What you described, "if the parent has a version, don't allow a child to
override it" is MENFORCER-19. I really do want the "draconian" version.
FWIW, I don't see it as particularly draconian, we just want all of our version
numbers to be in one file; developers who put version numbers in child nodes
are typically just ignorant of the policy. By failing the build we can be sure
that developers don't violate the policy by accident. It's sort of an
automated educational tool. :-)
> Fail the build if children declare dependency versions
> ------------------------------------------------------
>
> Key: MENFORCER-65
> URL: http://jira.codehaus.org/browse/MENFORCER-65
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Reporter: Dan Fabulich
>
> The opposite side of MENFORCER-19, it should be possible to require that
> children in a reactor NEVER declare any versions, but inherit all dependency
> versions from the parent's dependencyManagement. That is, if the parent
> fails to declare a certain dependency X, the child shouldn't be free to
> choose just any version; the child should have to add the dependency to the
> parent and then use the version declared there.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
