commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Kitching <skitch...@apache.org>
Subject Re: [ANNOUNCE][VFS] commons-vfs 1.0 RC1 available
Date Thu, 30 Jun 2005 23:29:02 GMT
On Thu, 2005-06-30 at 20:02 +0200, Mario Ivankovits wrote:
> Hi Simon!
> 
> Thanks for taking the time to check this all!!
> >Perhaps you could post your public GPG/PGP key so the signatures could
> >be checked too?
> >  
> Did you mean the KEYS file within the distribution? Or any other place?

Either would do. It's probably easiest if you just place your public key
up next to the RC files.

> >The unit test classes are shipped with the source distribution (as
> >usual), but running "maven" reports:
> ><output>
> >test:compile:
> >    [echo] No test source files to compile.
> >
> >test:test:
> >    [echo] No tests to run.
> ></output>
> >  
> All test are excluded as they need a complicated setup of some services.

Ok. Perhaps you could mention this in the RELEASE-NOTES.txt file? :-)

> 
> bin-distribution:
> >* no NOTICE.txt or RELEASE-NOTES.txt as for src
> >* no NOTICE.txt in jar's META-INF
> Is it optional to have it in META-INF or in the root?

Wherever the apache license is, a NOTICE file needs to be there too.

Both files should be in the root directory of the unpacked distribution.

Both files should also be in the META-INF directory of every jar file.
Unfortunately maven's default jar-building process only puts the
LICENSE.txt file there. This doc shows how to include it:
  http://jakarta.apache.org/commons/releases/prepare.html


Regards,

Simon


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


Mime
View raw message