The release plugin removed the license header in this commit, and it's
deployed to the Maven repo without one:
http://repo1.maven.org/maven2/org/apache/commons/commons-parent/1/
I wonder if moving the license inside the project element would
help, since the rest of the comments weren't removed.
On 11/18/06, Wendy Smoak [EMAIL PROTECTED] wrote:
The release plugin removed the license header in this commit, and it's
deployed to the Maven repo without one:
http://repo1.maven.org/maven2/org/apache/commons/commons-parent/1/
I wonder if moving the license inside the project element would
On 11/18/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 11/18/06, Wendy Smoak [EMAIL PROTECTED] wrote:
The release plugin removed the license header in this commit, and it's
deployed to the Maven repo without one:
http://repo1.maven.org/maven2/org/apache/commons/commons-parent/1/
I wonder if
Author: dennisl
Date: Sun Nov 12 12:36:46 2006
New Revision: 474035
URL: http://svn.apache.org/viewvc?view=revrev=474035
Log:
[maven-release-plugin] prepare release commons-parent-1
Modified:
jakarta/commons/proper/commons-parent/trunk/pom.xml
Modified:
