Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Tue, 1 Aug 2006 11:12:23 +0200
From: Jean-Baptiste Quenot <jbq@apache.org>
To: dev@cocoon.apache.org
Subject: Re: [Vote] Release 2.2M1
Message-ID: <20060801091222.GE70025@vision.anyware>
Mail-Followup-To: dev@cocoon.apache.org
References: <44CC77F7.3050207@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <44CC77F7.3050207@apache.org>
User-Agent: mutt-ng/devel-r804 (FreeBSD)

+0

I  don't  think  it's  a  good   idea  to  run  Cocoon  2.2  using
"mvn jetty6:run".  Basically if you use  Maven 2 you have no other
choice than running a beta version of Jetty.

I   made  some   tests  (outside   the  scope   of  Cocoon),   and
encountered  problems  with Jetty  6  Beta,  which appears  to  be
shaky.   If you  feel  confident, then  at least  be  sure to  use
version >= 6.0.0beta17.

But the point is:  it's not up to the build  system to decide what
servlet container  needs to be  used at runtime.  Do  you remember
Sylvain [1]talking about Ant+Ivy one and  a half year ago?  He was
right: Ivy *just*  downloads artifacts in a  local repository, and
that solves 99% of Maven 2 problems.  Ivy does little, but it does
it well.   In our current project  we [2]switched from Maven  2 to
Ant+Ivy recently, and life is much better now.  We trust the build
system again,  and we are able  to run any servlet  container like
before.

The good  news is that  Ivy is  compatible with Maven  2 directory
layout,  and  is  able  to  read POMs.   In  short,  it  does  not
require reorganizing  the source tree  all over again: it  is very
unintrusive.
-- 
     Jean-Baptiste Quenot
aka  John Banana Qwerty
http://caraldi.com/jbq/

[1] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=110569717619800&w=2
[2] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=115338484216107&w=2