commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar" <rahul.akol...@gmail.com>
Subject Re: [parent] svn commit: r635214
Date Thu, 13 Mar 2008 00:12:29 GMT
On 3/12/08, Dennis Lundberg <dennisl@apache.org> wrote:
> Niall Pemberton wrote:
>  > On Wed, Mar 12, 2008 at 10:36 PM, Dennis Lundberg <dennisl@apache.org> wrote:
>  >> Rahul Akolkar wrote:
<snip/>
>  >>  >
>  >>  > While this hadn't happened in recent commons-parent releases you did
>  >>  > (so the pom seemed set up exactly as needed, given prior discussions),
>  >>  > this release seems to have stripped out the license header again.
>  >
>  > Doh! OK thanks for pointing this out.
>  >
>  >>  > I'm not sure how important it is (for a pom release) and thereby, how
>  >>  > much effort should be spent in looking into this. Just seems a bit
>  >>  > displeasing that it would do that just in time for the tag :-)
>  >>  >
>  >>  > -Rahul
>  >>
>  >>  This can happen when the pom is altered during the release process. If
>  >>  only <version> and <scm> elements are altered, then it will be
OK. But
>  >>  if other parts gets modified you might be in trouble.
>  >
>  > I assume this is a know maven bug or shall I file an issue ticket?
>
>
> I think the bug is in the xml reader/writer that Maven uses. Found this
>  issue filed against the release plugin, which is similar although not
>  exactly the same.
>
>  http://jira.codehaus.org/browse/MRELEASE-289
>
<snap/>

Meanwhile, I added a little "background" section to the
CreatingReleases wiki page [1] for this.

-Rahul

[1] http://wiki.apache.org/commons/CreatingReleases

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message