[
https://jira.codehaus.org/browse/MRELEASE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302755#comment-302755
]
Robert Scholte commented on MRELEASE-685:
-----------------------------------------
Even with the implementation of the ability to add rules to the
maven-release-plugin, you still have to configure them. So you're just moving
the problem. And I'd prefer not to move more to the maven-release-plugin.
Companies and communities are the ones who care the most about licenses and
they should have a parent-pom where they can specify these things. OTOH, that's
probably also the place where the license is set.
> 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
