Return-Path: 
 <dev-return-9287-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: (qmail 17419 invoked from network); 16 Nov 2005 00:41:14 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 16 Nov 2005 00:41:14 -0000
Received: (qmail 94602 invoked by uid 500); 16 Nov 2005 00:41:13 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 94539 invoked by uid 500); 16 Nov 2005 00:41:13 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 94525 invoked by uid 99); 16 Nov 2005 00:41:13 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2005 16:41:13 -0800
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=URIBL_OB_SURBL
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [207.190.94.33] (HELO gadget.mwt.net) (207.190.94.33)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2005 16:41:03 -0800
Received: from [192.168.1.8] (dsl-67-41.westby.mwt.net [207.190.67.41])
	by gadget.mwt.net (8.12.11/8.12.11) with ESMTP id jAG0enZ2028106;
	Tue, 15 Nov 2005 18:40:49 -0600
Subject: Re: [mina] Using Ant + Forrest like Tapestry team does.
From: "John E. Conlon" <jconlon@verticon.com>
Reply-To: jconlon@verticon.com
To: erodriguez@apache.org
Cc: Apache Directory Developers List <dev@directory.apache.org>
In-Reply-To: <4379DF9F.8050806@apache.org>
References: <768dcb2e0511142357y3b199059j@mail.gmail.com>
	 <9e3862d80511150445g676647aayf401665a26bbd4ab@mail.gmail.com>
	 <4379DF9F.8050806@apache.org>
Content-Type: text/plain
Organization: Verticon, Inc.
Message-Id: <1132101649.4098.757.camel@trout>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) 
Date: 15 Nov 2005 18:40:49 -0600
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


> on the Felix project, one user stated coming from the Ivy/Ant setup...

Also (this user - yours truely) is currently using Apache Forrest for
internal project documentation as well.

My comment on 'light years' relates to the simplified approach to the
build that the central pom.xml of the M2-osgi-plugin gives me as well as
the ease of deployment/upgrade of OSGi bundles. The comment was by no
means meant as a knock against any of the other technologies. On the
contrary Ivy* and Forrest** each in its own sphere can accomplish more
than M2 for dependency management and documentation respectively. But
learning, keeping current, and maintaining the infrastructure has been a
challenge. Now I am still kicking the tires with M2/OSGi and have not
yet migrated my projects to from Ant/Ivy,Forrest, but I am hopeful that
if I need something special I could use the M2 plugin technology (now
Java based) to integrate with one or more of these technologies to get
what I currently have but in a more integrated fashion.

* Jayasoft (Home of Ivy) is on the JSR 277 expert group and hopefully
can help standardize some of their excellent Ivy technology features
which I expect will make their way into M2. 
See: http://jayasoft.org/ivy/doc/comparison for a comparison of Ivy to
other technologies including M1 & M2.


** Forrest (sub project of Cocoon)
Currently I call Forrest in my ANT builds with:
<target 
       name="docs" 
       depends="test, javadocs, jdepend, generate-docs, doc-schema,
build-docs" 
       description="Builds all the documentation.">
          <ant antfile="${env.FORREST_HOME}/forrest.antproxy.xml"    
               target="site"/>
</target>

So I expect even with out doing M2 plugins it will be easy to call
forrest's ant build from M2 if I have to.
Another positive development is that the Forrest/Cocoon dev folks are,
like ApacheDS moving toward OSGi, so we can all look forward to having
Cocoon bundles in the OSGi quiver when heavy duty production XML/XSL
pipelining is needed. 

thanks again to all the ApacheDs/Mina team,
John


On Tue, 2005-11-15 at 07:16, Enrique Rodriguez wrote:
> Brett Porter wrote:
> > On 11/15/05, Trustin Lee <trustin@gmail.com> wrote:
> > 
> >>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)
> 
> Trustin,
> 
> I am finding Maven 2 to be many times better than Maven 1 and I have 
> been moving in the direction that we were going to use Maven 2 on 
> Directory.  I'm not sure what you're looking for for documentation, but 
> I've figured out what I've needed from looking at other POM examples, 
> notably the ones in Plexus and Maven 2 SVN, and from directly asking 
> Brett Maven 2 questions on IRC.  For functionality not yet in Maven 2 I 
> have been writing plugins (in Java), which I never did for Maven 1 on 
> account of Jelly.
> 
> I only have 1 data point and no personal experience with Ivy, but over 
> on the Felix project, one user stated coming from the Ivy/Ant setup to 
> Maven 2/OSGi and finding "My whole development workflow is light years 
> ahead of my previous ant/nano container/ivy environment."
> 
> Enrique
>