Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 5976 invoked from network); 15 Nov 2005 07:58:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Nov 2005 07:58:03 -0000 Received: (qmail 48930 invoked by uid 500); 15 Nov 2005 07:58:02 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 48879 invoked by uid 500); 15 Nov 2005 07:58:02 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 48868 invoked by uid 99); 15 Nov 2005 07:58:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Nov 2005 23:58:01 -0800 X-ASF-Spam-Status: No, hits=0.9 required=10.0 tests=HTML_10_20,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of trustin@gmail.com designates 64.233.184.202 as permitted sender) Received: from [64.233.184.202] (HELO wproxy.gmail.com) (64.233.184.202) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Nov 2005 23:57:53 -0800 Received: by wproxy.gmail.com with SMTP id 57so1175921wri for ; Mon, 14 Nov 2005 23:57:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=RUO0AGyExvaI+dN2KnOAYJ+kWEXK6FV6ozvcXn9QIjbcTqucGhERifPvKTs+s7M0uvICHVyKG1JRD/P1xcOXrv1LJl/ofNGPe6TuAkrsAOGreod6qbHfAJ7FYuuXVdvUCDFNjNx1PJIh211igaH+sfA5Sm1rwHFGdUy/GtitGUs= Received: by 10.54.100.2 with SMTP id x2mr4009334wrb; Mon, 14 Nov 2005 23:57:40 -0800 (PST) Received: by 10.54.127.2 with HTTP; Mon, 14 Nov 2005 23:57:40 -0800 (PST) Message-ID: <768dcb2e0511142357y3b199059j@mail.gmail.com> Date: Tue, 15 Nov 2005 16:57:40 +0900 From: Trustin Lee To: Apache Directory Developers List Subject: [mina] Using Ant + Forrest like Tapestry team does. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9002_18326916.1132041460557" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_9002_18326916.1132041460557 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi all, I've been playing with Maven 2 and splitting MINA into multiple projects. But at this time, Maven 2 documentation is far from perfection, and we have to bother Maven team and manuals to build a satistifiable build system for MINA (and of course for other projects of us) While I'm looking for the Apache projects which uses EasyMock to clarify some license issue with MIT-license, I've found that Tapestry team adopted Ant + Forrest instead of Maven. This way has an apparent advantage for MINA= : 1) We can easily package multiprojects into one tarball. 2) We can generate various versions of multiprojects; mina-all, mina-core, mina-ssl, ... And, we can distribute all the JARs in one tarball with no effort. 3) We don't need to worry about generating one site documentation for multiprojects such as delegating JavaDocs and other reports. 4) Forrest provides better document generation. There are some downside for it, too: 1) We cannot use Maven repository. Actually we can, but we have to assume that Maven Ant bridge is installed for a user's computer. 2) We cannot use Maven deployment feature. But I think this is OK because we can just use Maven-Ant bridge or JAM ( http://www.javagen.com/jam/index.html). WDYT? Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ ------=_Part_9002_18326916.1132041460557 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi all,

I've been playing with Maven 2 and splitting MINA into multi= ple projects.  But at this time, Maven 2 documentation is far from per= fection, and we have to bother Maven team and manuals to build a satistifia= ble build system for MINA (and of course for other projects of us)

While I'm looking for the Apache projects which uses EasyMock to cl= arify some license issue with MIT-license, I've found that Tapestry team ad= opted Ant + Forrest instead of Maven.  This way has an apparent advant= age for MINA:

1) We can easily package multiprojects into one tarball.

2) = We can generate various versions of multiprojects; mina-all, mina-core, min= a-ssl, ... And, we can distribute all the JARs in one tarball with no effor= t.

3) We don't need to worry about generating one site documentation f= or multiprojects such as delegating JavaDocs and other reports.

4) F= orrest provides better document generation.

There are some downside = for it, too:

1) We cannot use Maven repository.  Actually we can, but we ha= ve to assume that Maven Ant bridge is installed for a user's computer.
<= br>2) We cannot use Maven deployment feature.

But I think this is OK= because we can just use Maven-Ant bridge or JAM ( http://www.javagen.com/ja= m/index.html).

WDYT?

Trustin
--
what we call human= nature is actually human habit
--
http://gleamynode.net/ ------=_Part_9002_18326916.1132041460557--