[
http://jira.codehaus.org/browse/MENFORCER-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159056#action_159056
]
Brett Porter commented on MENFORCER-41:
---------------------------------------
I think so too... even if the changes plugin is providing rules for the
enforcer plugin to utilise, the enforcer can't grow limitlessly with plugin
config testing.
Can we close this as won't fix?
> Enforcer rules for ChangesFileExists and ChangesFileHasPomVersion
> -----------------------------------------------------------------
>
> Key: MENFORCER-41
> URL: http://jira.codehaus.org/browse/MENFORCER-41
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
> Reporter: Ben Lidgey
> Assignee: Brian Fox
> Attachments: MavenEnforcerChangesRules.zip
>
>
> New code to implement two rules:
> * ChangesFileExists -- checks there is a src/changes/changes.xml file
> * ChangesFileHasPomVersion -- checks the changes.xml has an entry with a
> version matching the current version in the pom.
--
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
