Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <47845DC3.2080006@dslextreme.com>
Date: Tue, 08 Jan 2008 21:38:11 -0800
From: Ralph Goers <Ralph.Goers@dslextreme.com>
Reply-To: rgoers@apache.org
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Question about sample site in trunk
References: <4781D575.60301@dslextreme.com>
 <315091D3-B792-4B79-AFF6-89105D6361F2@reverycodes.com>
 <47831974.7050906@dslextreme.com>
 <C259A670-F765-4086-A2E9-5B4CC109CE65@reverycodes.com>
 <4783D2BE.5030403@apache.org> <4784516C.8040704@gmx.de>
 <47845775.1090107@dslextreme.com> <47845C37.4040803@gmx.de>
In-Reply-To: <47845C37.4040803@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

No. We could take advantage of http://maven.apache.org/ant-tasks.html to 
create various ant scripts to do that.  However, since I'm still not 
sure what this supposed support for non-maven builds really looks like 
it is hard to have a good answer to the question.

Ralph

Joerg Heinicke wrote:
> On 09.01.2008 00:11, Ralph Goers wrote:
>
>> Maybe we are on the same page, but I'm unclear what you mean by 
>> "include".  A cocoon release should consist of nothing more than 
>> deploying artifacts to the maven repository. End users should be 
>> getting the release by specifying the version number of the release 
>> in the archetypeVersion.
>
> That's exactly what I don't want to have as ONLY option. IMO we must 
> provide the classic kind of a release. Otherwise a comment like we are 
> going to put into the FAQ ("You really don't need Maven!") is also 
> just a joke. Should one grab each jar from the Maven repository by hand?
>
> Joerg