Issue Type: Improvement Improvement
Assignee: Unassigned
Components: extra-enforcer-rules
Created: 09/Sep/13 3:26 PM
Description:

I would like to use <enforceBytecodeVersion> to ensure that most of my project is compatible with Java 5. However there are a handful of Java 6-based dependencies used only under special circumstances (e.g. after a dynamic version check), or only with <scope>test</scope>, etc., and I would like to exclude these from the check. Unfortunately this enforcer rule does not currently seem to offer any way to do that. I would expect an <excludes> and <includes> similar to other dependency rules. (AbstractBanDependencies could I suppose define these parameters, but that would probably clash with existing subclasses.)

Could try to write a patch if you agree this makes sense. (Diff attached to JIRA? GitHub pull request? I am a Mojo committer, so could also commit to trunk.)

Project: Mojo
Priority: Major Major
Reporter: Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to