Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <4469A8BD.305@apache.org>
Date: Tue, 16 May 2006 12:26:05 +0200
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: What does a Cocoon 2.2 release consist of?
References: <44683A68.5060706@dslextreme.com> <e4agtu$nnh$1@sea.gmane.org>
 <4469995E.5040403@apache.org> <44699C51.6070901@apache.org>
 <44699DCE.7060206@apache.org>
In-Reply-To: <44699DCE.7060206@apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Reinhard Poetz wrote:
> Carsten Ziegeler wrote:
> 
>> As important as what the release should consist of is what the release
>> should not contain. Imho we should remove all OSGi related stuff from
>> the release to not confuse users.
> 
> I think this causes a lot of work without a benefit. As you said some time ago, 
> user don't look into the internals of jars, they just want to use them.
:) - As long as this is hidden in a jar, I'm fine. But what about
configuration files
like wiring.xml lying in the root directory? And I don't want to ship
OSGi related jars (I know with maven we don't technically ship them).

Carsten
-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/