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-configuration-test has an issue affecting its community
integration.
Thi
Also, it would help to know what Maven command-line was used to build
the release (and on which OS), so it can readily be checked on other
systems / OSes.
The README file could perhaps be updated with this information - at
the moment it only describes how to build the site.
On 04/10/2008, sebb <[
The source and javadoc jars don't have LICENSE and NOTICE files.
The NET_2_0 tag does not agree with the source file archive - the pom
files differ.
Which pom was actually used to generate the release?
On 04/10/2008, Rory Winston <[EMAIL PROTECTED]> wrote:
> Guys
>
> I know commons has been dyi
James
Thats a good idea, I'll do that...I'll recut and retag a new release and
send out a new vote thread later on today. I did create a release tag
which I had been reusing, but I think in retrospect I should have just
created more RC tags.
Thanks
Rory
James Carman wrote:
How about sendin
How about sending out a fresh [vote] thread email again? I don't tend
to keep stuff around and it's hard to know what we're voting on when
new versions of the rc keep getting uploaded. If you're cutting a new
release candidate, I'd say you should upload it, but don't overwrite
what you put out th
Guys
I know commons has been dying a slow death due to inactivity, but
binding votes (either +-1) would be appreciated. I want to get this out
finally...
Rory Winston wrote:
Ah, yes, you're right -Prc does actually generate them
automatically. That explains the discrepancy.
I have uplo
