[
https://jira.codehaus.org/browse/MRELEASE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302590#comment-302590
]
Martin Todorov commented on MRELEASE-685:
-----------------------------------------
The thing is... if people care enough to actually add the enforcer plugin and
explicitly add a rule (which currently doesn't exist) for checking if the
project has a <license/>, then they would most-likely already have defined it,
as they would be diligent enough.
Something I've been thinking of for a while is that the release plugin needs to
have the option of defining <rules> just like the enforcer plugin. Then it
would be possible to write your own custom checks and attach them to the
release:prepare goal for example.
> prompt for license information while release:perform
> ----------------------------------------------------
>
> Key: MRELEASE-685
> URL: https://jira.codehaus.org/browse/MRELEASE-685
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: prepare
> Reporter: Mark Struberg
>
> Currently not many projects make use of the <license> tags available in
> pom-4.0, but this information might be used for many things.
> I imagine something like an automated 'license verification check' e.g. with
> the maven-dependency-plugin
> $> mvn dependency:licenses
> which lists all the dependencies with their licenses.
> Apache RAT could also make use of this information IF the <license> coverage
> would be good enough!
> To increase the amount of pom files with a valid <license> section, we could
> prompt for it in the release:prepare step and create the respective <license>
> section for the user.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
