![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
extra-enforcer-rules |
|
Created:
|
09/Apr/13 4:24 PM
|
|
Description:
|
For OSGi compliance where it is important that packages are defined within
(and exported from) a single artifact, it would be great to
be able to enforce that groupId and package (and optionally parts of the VCS path) adheres to naming standards.
Simplified:
Given a project with groupId com.foo.bar, all Classes/Interfaces/Annotations in the project should reside within or in sub-packages to com.foo.bar. A class com.foo.bar.gnat.Boo would be legal, and a class com.foo.Baz would be illegal.
Moreover, I would suggest an optional additional validation to verify that the project should reside at the path com/foo/bar within its VCS. This validation rule would go a long way to enforcing proper naming standards in large-scale projects.
|
|
Project:
|
Mojo
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Lennart Jorelid
|
|
|
|
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
