Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <425EBEBD.5020500@upaya.co.uk>
Date: Thu, 14 Apr 2005 20:04:29 +0100
From: Upayavira <uv@upaya.co.uk>
User-Agent: Debian Thunderbird 1.0 (X11/20050116)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Do we want a GUI installer?
References: <200504141751.j3EHpcjM009769@mira.taygeta.com>
	 <425EB698.1060706@upaya.co.uk> <cc159a4a05041411432ec2185d@mail.gmail.com>
In-Reply-To: <cc159a4a05041411432ec2185d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Peter Hunsberger wrote:
> On 4/14/05, Upayavira <uv@upaya.co.uk> wrote:
> 
>>Skip Carter wrote:
>>
>>>I'd rather not see one.  At least if one is developed,
>>>there needs remain to be a way to install from the command
>>>line.  ALL of my cocoon installations are on headless systems,
>>>and some of them are remote, so a GUI is not really very practical.
>>
>>There is no way that such an installer would replace the current system,
>>merely augment it. This installer is nothing more than a wrapper around
>>our existing Ant scripts anyway. After all, many Cocoon installations
>>are on headless servers. The intention was to smooth over that early
>>stage of usage when someone is at the beginning of learning Cocoon.
>>Throwing them into having to copy and edit text files when they first
>>start IMO introduces complexity that they could well do with learning a
>>little later in their involvement with Cocoon.
>>
>>But, having said that, it doesn't seem like people are that keen on the
>>idea anyway.
> 
> 
> I think without the license problems people might be in favour or
> least neutral.
> 
> Perhaps you could include the config script with Cocoon with a pointer
> to the Source Forge project?  Alternately, maybe you could donate the
> config file to the Source Forge project and include something in the
> Cocoon docs...

Without a fix to the licencing problems, I ain't taking this any 
further. The author is willing to relicense, it is just a question of 
how embedded his other jars are into his code.

Regards, Upayavira