Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=RUD6KhVkBum3s6EQcj2mvNRS6Gvqnn7CzY0pZyAl72TBY6Ogg3H45AEc+vXRfxw1KwD1gT/V1ltNyV7mjg3KKd4SERCnUSNrCrXBV157g0N762uRZra4GYwPb8w9624wXsmnbLeJAe4oSM+IR6KRtrdo9RV7c2yzf2wzAnZAmOk=
Message-ID: <451BEB5C.1060907@gmail.com>
Date: Thu, 28 Sep 2006 17:33:48 +0200
From: hepabolu <hepabolu@gmail.com>
Reply-To: hepabolu@gmail.com
User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Maven info wanted
References: <451A567A.4@gmail.com> <451A7817.8020003@apache.org>
 <20060927135135.GA55588@vision.anyware> <451BB815.2090905@nada.kth.se>
 <451BBBBB.30307@apache.org> <451BC626.7080301@apache.org>
In-Reply-To: <451BC626.7080301@apache.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Reinhard Poetz said the following on 28/9/06 14:55:

> We have invested a lot of time into making trunk build with M2. And 
> don't forget that it's much more than just compiling the thing.
> 
> We have two archetypes, one deployment plugin, the documentation which 
> is exported using Maven, a working integration build, reports and 
> certainly much more. Also don't forget that releasing a Cocoon artifact 
> has become very simple. And one last point: If you build Cocoon using 
> some different build system I think that we cannot forbear providing 
> Maven 2 metadata files (pom.xml) because many developers will ask for them.

As said: I really don't care as long as I'm able to figure out how 
things work. For now I'm stuck on a 'build failure' on the line
"$mvn clean install eclipse:clean eclipse:eclipse" as described in
http://cocoon.zones.apache.org/daisy/documentation/g1/756.html

and I have no clue where to go and find more info.

I'll settle for Maven but then we need to devote considerable hackathon 
time to proper documentation. I don't mind doing corrections or writeups 
or whatever else that's needed to make documentation a coherent piece, 
but I need the initial info from you guys.

Bye, Helma