You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Julien Vermillard <jv...@archean.fr> on 2008/08/12 17:07:54 UTC
Download page and structures of release tarballs
Hi,
I updated a bit the download page :
http://mina.apache.org/downloads.html
I hope it less confusing about downloading and signature checking.
Feedback welcome!
Secondly, our current release tarballs are quite messy, you got sources
and binaries jar in the root, and you got sources in each sub modules
directory, for an examples :
http://mina.apache.org/dyn/closer.cgi/mina/2.0.0-M3/mina-2.0.0-M3.tar.bz2
I would like to propose something different :
- a "binaries" directory for .jar binaries
- a "sources" directory for sources of all the modules and with the
pom.xml files for building with maven
- a "docs" directory for docs (javadoc and xref)
- licences & notices in root directory
Here an example :
http://people.apache.org/~jvermillard/mina-2.0.0-M4-SNAPSHOT.tar.bz2
We still miss :
- a good README.txt file
- a "lib" directory for all the dependencies (anyone know how to do
that with automagicly with mvn ?)
- RATS report for Niklas :)
WDYT ?
Julien
Re: Download page and structures of release tarballs
Posted by Mark Webb <el...@gmail.com>.
sounds good to me.
+1 to organization :)
On Tue, Aug 12, 2008 at 11:07 AM, Julien Vermillard
<jv...@archean.fr>wrote:
> Hi,
>
> I updated a bit the download page :
> http://mina.apache.org/downloads.html
> I hope it less confusing about downloading and signature checking.
> Feedback welcome!
>
> Secondly, our current release tarballs are quite messy, you got sources
> and binaries jar in the root, and you got sources in each sub modules
> directory, for an examples :
> http://mina.apache.org/dyn/closer.cgi/mina/2.0.0-M3/mina-2.0.0-M3.tar.bz2
>
> I would like to propose something different :
> - a "binaries" directory for .jar binaries
> - a "sources" directory for sources of all the modules and with the
> pom.xml files for building with maven
> - a "docs" directory for docs (javadoc and xref)
> - licences & notices in root directory
>
> Here an example :
> http://people.apache.org/~jvermillard/mina-2.0.0-M4-SNAPSHOT.tar.bz2<http://people.apache.org/%7Ejvermillard/mina-2.0.0-M4-SNAPSHOT.tar.bz2>
>
> We still miss :
> - a good README.txt file
> - a "lib" directory for all the dependencies (anyone know how to do
> that with automagicly with mvn ?)
> - RATS report for Niklas :)
>
> WDYT ?
>
> Julien
>
Re: Download page and structures of release tarballs
Posted by "W.B. Garvelink" <ba...@gmail.com>.
I'm halfway through changing release.xml for this. I'll submit a patch
later tonight.
Barend
On Tue, Aug 12, 2008 at 9:03 PM, Niklas Gustavsson <ni...@protocol7.com> wrote:
> On Tue, Aug 12, 2008 at 5:07 PM, Julien Vermillard
> <jv...@archean.fr> wrote:
>> I would like to propose something different :
>> - a "binaries" directory for .jar binaries
>> - a "sources" directory for sources of all the modules and with the
>> pom.xml files for building with maven
>> - a "docs" directory for docs (javadoc and xref)
>> - licences & notices in root directory
>
> How about doing separate binary and source tarballs?
>
>> We still miss :
>> - a "lib" directory for all the dependencies (anyone know how to do
>> that with automagicly with mvn ?)
>
> You can check how I did it for FtpServer, as Barend suggested below I
> use the maven-assembly-plugin.
>
>> - RATS report for Niklas :)
>
> Woho! Again, feel free to use what I've done in FtpServer.
>
> /niklas
>
Re: Download page and structures of release tarballs
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Tue, Aug 12, 2008 at 5:07 PM, Julien Vermillard
<jv...@archean.fr> wrote:
> I would like to propose something different :
> - a "binaries" directory for .jar binaries
> - a "sources" directory for sources of all the modules and with the
> pom.xml files for building with maven
> - a "docs" directory for docs (javadoc and xref)
> - licences & notices in root directory
How about doing separate binary and source tarballs?
> We still miss :
> - a "lib" directory for all the dependencies (anyone know how to do
> that with automagicly with mvn ?)
You can check how I did it for FtpServer, as Barend suggested below I
use the maven-assembly-plugin.
> - RATS report for Niklas :)
Woho! Again, feel free to use what I've done in FtpServer.
/niklas
Re: Download page and structures of release tarballs
Posted by "W.B. Garvelink" <ba...@gmail.com>.
On Tue, Aug 12, 2008 at 5:07 PM, Julien Vermillard
<jv...@archean.fr> wrote:
> We still miss :
> - [...]
> - a "lib" directory for all the dependencies (anyone know how to do
> that with automagicly with mvn ?)
- Using maven-assembly-plugin: add a DependencySet element to release.xml.
- Using maven-dependency-plugin: use the copy-dependencies task.
I'd recommend the former.
Barend