Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 59771 invoked by uid 500); 29 Oct 2002 13:03:53 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 59760 invoked from network); 29 Oct 2002 13:03:53 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Torsten Curdt Organization: dff internet & medien To: cocoon-dev@xml.apache.org Subject: Re: [vote] build systems Date: Tue, 29 Oct 2002 14:06:00 +0100 User-Agent: KMail/1.4.3 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200210291406.00533.tcurdt@dff.st> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Argh, but it did work, because when I created the portal block > I took care of the build system and changed it for that. > > Yes I confirm now it doesn't work anymore, so we should fix it. yepp! the cocoon.jar is build first and then the roles get applied... so in the build dir there is the correct cocoon.roles in the end :-/ BTW: I just found doing a plain "build" gives me the same esql problem yo= u=20 just reported while "build installwar" works just fine *sigh* > > If you just want to add a new block - you wouldn't have to > > rebuild the core > > but compile that block which will produce the block and update > > the roles.jar. > > I feared that you would say this, but this reminds me of a poor-mans > concept of blocks. thankyou! *moping* =2E..at least it will work - the roles is a plague anyway. > > then let's at least polish the current build system a little... > > Yupp! That's all I wanted. But once you set ball rolling... ;-) -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org