[
http://jira.codehaus.org/browse/MENFORCER-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127260
]
Ben Lidgey commented on MENFORCER-41:
-------------------------------------
Surely the Enforcer plugin is a framework for writing rules?
In ChangesFileExists I have hard coded the location of the changes.xml as this
is a first version. I agree for flexibility the location could be
parameterised.
I was not aware of the RequireFilesExist rule.
ChangesFileHasPomVersion: it will fail the build regardless of whether reports
are run or not. Moving it into the Changes plugin though would make sense from
the parsing point of view though.
> 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
