This happens when Maven rewrites the pom file during release. I'm sure
why, but I have devised a workaround for it. Before doing the actual
release, do the following:
1. mvn release:prepare -DdryRun=true
2. Compare pom.xml with pom.xml.tag
3. Make sure you copy all the changes, except for changes
On 12/22/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> Rahul Akolkar wrote:
>
> >
> > Yup, the pom gets distributed (as part of maven doing what it does),
> > so having a license header seems important. However, the m2 release
> > plugin strips it out [1] sometimes (no one clarified why or how to
Rahul Akolkar wrote:
> On 12/22/07, Oliver Heger <[EMAIL PROTECTED]> wrote:
>
>>
>> - The pom.xml is missing the license header.
>>
>
>
> Yup, the pom gets distributed (as part of maven doing what it does),
> so having a license header seems important. However, the m2 release
> plugin strips it
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jaxme has an issue affecting its community
integration.
This
On 12/22/07, Oliver Heger <[EMAIL PROTECTED]> wrote:
>
> - The pom.xml is missing the license header.
>
Yup, the pom gets distributed (as part of maven doing what it does),
so having a license header seems important. However, the m2 release
plugin strips it out [1] sometimes (no one clarified wh
Hi,
the artifacts look good to me. I found the following issues:
- The pom.xml is missing the license header.
- The maven 1 build declares its version as 1.3-SNAPSHOT and has a
dependency to commons-io 1.4-SNAPSHOT. In the section an
element for the current release is missing.
- The ant bu
