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: <41E66B5D.6080505@nada.kth.se>
Date: Thu, 13 Jan 2005 13:36:45 +0100
From: Daniel Fagerstrom <danielf@nada.kth.se>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [RT] Update to build system: location of blocks and gump
References: <41E66800.2040506@apache.org>
In-Reply-To: <41E66800.2040506@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Carsten Ziegeler wrote:

> I'm currently thinking about making the build system able to include 
> blocks from "external" locations, which means blocks that are not 
> directly in the cocoon directory.

Excelent!

> I'm thinking of a simple but working solution: I guess the easiest way 
> would be to just add the root directory for a block to our gump 
> descriptor. Currently the build system assumes that a block is located 
> at src/blocks/BLOCKNAME.
> When the build system uses this information from gump.xml, we can 
> simply include a "local.gump.xml" containing some more projects into 
> the gump.xml and build an aggregated description that is only used by 
> the build process. Gump itself is not affected as it still uses the 
> gump.xml.

Sounds reasonable. You might also want to take a look at 
http://issues.apache.org/bugzilla/show_bug.cgi?id=32212, that allow for 
declaring external blocks in local.blocks.properties. The patch still 
requires changes to gump.xml, so your approach seem more convinient.

> So my questions are:
> - Is there a possibility in gump to define the root directory for a 
> block?
> - Does this change have any impact on other parts that I oversee?

Don't know.

/Daniel