You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Mario Ivankovits <ma...@ops.co.at> on 2005/06/29 21:52:54 UTC
[ANNOUNCE][VFS] commons-vfs 1.0 RC1 available
Hi!
The commons vfs community is happy to announce the availability of
commons-vfs 1.0 RC1.
Please find the RC at
http://people.apache.org/~imario/vfs
The site can be reviewed at
http://people.apache.org/~imario/vfs-1.0-RC1/site
This is my first release so please forbear with me about the things I
might have done wrong.
---
Mario
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [ANNOUNCE][VFS] commons-vfs 1.0 RC1 available
Posted by Simon Kitching <sk...@apache.org>.
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
Re: [ANNOUNCE][VFS] commons-vfs 1.0 RC1 available
Posted by Mario Ivankovits <ma...@ops.co.at>.
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?
>=== src.tar.gz
>
>The NOTICE.txt file is missing from the src distribution.
>
>A RELEASE-NOTES.txt file should also be included.
Ok, will look at it.
>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.
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?
> ... Documentation ...
All documentation problems fixed for next release (RC2) as suggested.
>Public interface o.a.c.vfs.FileName generally omits the scope
>declarations (ok, as all declarations are implicitly public in an
>interface). However there is one method "getRoot" explicitly declared
>public, which is a little inconsistent.
Ok, will change it. I prefer to explicit declare modifiers.
>=== final comments
>
>commons-vfs looks like a very impressive piece of work! Congratulations
>to all the developers!
>
Thanks!
Ciao,
Mario
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [ANNOUNCE][VFS] commons-vfs 1.0 RC1 available
Posted by Simon Kitching <sk...@apache.org>.
Hi Mario,
On Wed, 2005-06-29 at 21:52 +0200, Mario Ivankovits wrote:
> Hi!
>
> The commons vfs community is happy to announce the availability of
> commons-vfs 1.0 RC1.
>
> Please find the RC at
> http://people.apache.org/~imario/vfs
>
> The site can be reviewed at
> http://people.apache.org/~imario/vfs-1.0-RC1/site
>
>
> This is my first release so please forbear with me about the things I
> might have done wrong.
=== checksums/signatures
Checksums all appear ok.
Perhaps you could post your public GPG/PGP key so the signatures could
be checked too?
=== src.tar.gz
The NOTICE.txt file is missing from the src distribution.
A RELEASE-NOTES.txt file should also be included.
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>
The jar file build from the src distribution should have a NOTICE.txt
file in the META-INF directory.
Many commons components arrange for the foo-x.y-src distribution to
unpack into a directory with name foo-x.y-src rather than foo-x.y. This
certainly isn't mandatory. However if you do want to do that,
instructions on how to do this are at the (recently updated) release
preparation page:
http://jakarta.apache.org/commons/releases/prepare.html
=== src.zip
All looks ok (only same notes as above)
=== tar.gz (binary)
* no NOTICE.txt or RELEASE-NOTES.txt as for src
* no NOTICE.txt in jar's META-INF
== site
= overview page
needet -> needed
= download page
needet -> needed
nigtlies -> nightlies
The link titled "Check the source out of SVN, as described ..." is
rather unhelpful.
The link to maven is obsolete; maven is now at maven.apache.org.
= ant tasks page
This says:
"To use the Ant tasks, copy commons-jar.jar and its dependencies..."
should this perhaps be "..copy commons-vfs.jar ..."?
= development page
needet --> needed
= mailing lists page
For some reason, the archive link points to
"mail-archives.eu.apache.org". Perhaps it should point to
"mail-archives.apache.org"?
= source repository page
This just points to the base of the entire apache SVN tree. It would be
nice for this to point to the commons-vfs base directory.
= reports
I recommend disabling the changelog, developer activity and file
activity reports. These aren't of any great use, and given that
date-based selection is stuffed in the apache SVN repo due to CVS
imports they can in fact be wrong.
The clover report link appears broken.
There's an odd "Jelly Tag Documentation" report link there I haven't
seen before. And the content is basically empty. Perhaps this should be
removed?
=== final comments
commons-vfs looks like a very impressive piece of work! Congratulations
to all the developers!
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [ANNOUNCE][VFS] commons-vfs 1.0 RC1 available
Posted by Simon Kitching <sk...@apache.org>.
On Wed, 2005-06-29 at 21:52 +0200, Mario Ivankovits wrote:
> Hi!
>
> The commons vfs community is happy to announce the availability of
> commons-vfs 1.0 RC1.
>
> Please find the RC at
> http://people.apache.org/~imario/vfs
>
> The site can be reviewed at
> http://people.apache.org/~imario/vfs-1.0-RC1/site
>
>
I see the javadocs have been generated with all private and
package-scope members/methods also included. I suggest that this should
be turned off; it's a lot of info not relevant to users.
Just in passing I noticed the following too:
Public interface o.a.c.vfs.FileName generally omits the scope
declarations (ok, as all declarations are implicitly public in an
interface). However there is one method "getRoot" explicitly declared
public, which is a little inconsistent.
Same for FileObject ("canRenameTo").
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org