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)
Message-ID: <446C86FF.1020700@odoko.co.uk>
Date: Thu, 18 May 2006 15:38:55 +0100
From: Upayavira <uv@odoko.co.uk>
Organization: Odoko Ltd
User-Agent: Thunderbird 1.5 (X11/20060309)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: CocoonTask
References: <446C6203.6070209@apache.org> <446C7080.20809@apache.org>
 <446C7B17.6080700@odoko.co.uk> <446C8492.5010403@apache.org>
In-Reply-To: <446C8492.5010403@apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Reinhard Poetz wrote:
> Upayavira wrote:
>> Carsten Ziegeler wrote:
>>
>>> Reinhard Poetz wrote:
>>>
>>>> I was going through the list of dependencies because I was wondering
>>>> why we have Ant artifacts in our web applications. I found the cause
>>>> which is the CocoonTask and the question is, what we want to do with
>>>> it. As IMO it shouldn't be part of a Cocoon core, I see two options:
>>>>
>>>>  - create a "cocoon-ant" module
>>>>  - remove it
>>>>
>>>> BTW, is it supposed to work with Cocoon 2.2 at all?
>>>>
>>>
>>> I guess it's currently not working anyway. Personally I see no real need
>>> in a cocoon ant task, so I would vote for removing it. There is forrest
>>> anyway.
>>
>>
>> It likely isn't working, and would need the same attention as the CLI.
>>
>> I don't agree with the 'there is forrest' argument, as Forrest should be
>> using the Ant task rather than calling the CLI.
>>
>> The Cocoon Ant task is really a better way of using the CLI. So by
>> saying there's no need for the Ant task, you're effectively also saying
>> there's no need for the CLI either. (Now that may well be true, wget and
>> all, but that's a different discussion).
>>
>> However, moving it into a separate module makes sense, as both CLI and
>> Ant are definitely not the main use-cases for Cocoon.
>>
>> In the end, if no-one is prepared to update it, then it would be better
>> removed. And I'm not going to be in a position to update it myself.
> 
> What about creating a cocoon-cli module that also contains the Ant task?
> I can do the move in our repo but I don't have the knowledge (and time)
> to test it.

I'm quite happy with that.

Do note that the CocoonTask is nothing but a wrapper around the
CocoonBean, much as is the CLI (org.apache.cocoon.Main). Were you to get
the CocoonBean working without changing its interfaces, the CocoonTask
would start working again. Once someone has worked out the CLI, the ant
task should be pretty simple.

There was an older Ant task in the scratchpad that was a rewrite of the
CLI - but I think/hope that was deleted long ago.

Regards, Upayavira