You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Nathan Bubna (JIRA)" <de...@velocity.apache.org> on 2007/02/23 19:06:09 UTC
[jira] Resolved: (VELOCITY-518) Veloctiy poms should have a
section
[ https://issues.apache.org/jira/browse/VELOCITY-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-518.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5
Ok.
> Veloctiy poms should have a <licenses> section
> ----------------------------------------------
>
> Key: VELOCITY-518
> URL: https://issues.apache.org/jira/browse/VELOCITY-518
> Project: Velocity
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.0b1, 1.0b2, 1.0b3, 1.0-Release, 1.1-rc1, 1.1-rc2, 1.1, 1.2, 1.3-rc1, 1.3, 1.3.1-rc2, 1.3.1, 1.4, 1.5 beta1, 1.5 beta2
> Reporter: Daniel Kulp
> Fix For: 1.5
>
>
> A licenses section should be added to the velocity poms. It should look something like:
> <licenses>
> <license>
> <name>The Apache Software License, Version 2.0</name>
> <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
> <distribution>repo</distribution>
> </license>
> </licenses>
> The maven team is working on using that information in several plugins to help validate releases. (Example: there could be an apache validate plugin that makes sure all the licenses of dependencies are OK for apache to release)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org