[
https://issues.apache.org/jira/browse/VELOCITY-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474864
]
Nathan Bubna commented on VELOCITY-518:
---------------------------------------
To my knowledge, Velocity has never released a POM as an independent artifact.
We have only had a pom.xml in a release since the 1.5-beta1 release. This
pom.xml had the requested license section. Prior to that we had a maven1
project.xml that did not contain license information. That project.xml was
only included in the 1.4 release.
We can't retroactively modify previous releases in the archives. We have no
plans (or desire that i'm aware of) to release POMs for all the "affected
versions" you list. In fact, i'm not currently aware of us planning to
release a POM independent of our standard distribution at all, and if we do, it
will be based on our current pom.xml which has had the license info from its
inception.
So, what exactly is it that you expect us to do here that prompts you to list
this as a major bug? Without some more direction, i'm inclined to resolve this
as Invalid or Incomplete.
> 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
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
