[mojo-dev] [jira] (MOJO-1841) Contrary to documentation requiredRoles are not always valid

[Andreas Sewe (JIRA)]

Andreas Sewe commented on MOJO-1841 Contrary to documentation requiredRoles are not always valid OK, reconstructing my thoughts from back then: The "problem" is exemplified in <https://bitbucket.org/scalabench/scalabench-parent/src/974afdcefaa61af1a8dc9cd7b83eeaae8b3aea5a/pom.xml?at=1-SNAPSHOT#cl-401>; I did need to specify the "Project Founder" role twice, once in requireRoles and once in validRoles. From the "requiredRoles are always valid" piece of documentation I would assume that this repetition was unnecessary, as a required role must be valid in order to be useful. (FWIW, requiredRoles and optionalRoles would be better names for this interpretation.) Hope this clarifies things.

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