cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <bdelacre...@codeconsult.ch>
Subject Re: unstable blocks (was: [VOTE] Move javaflow into scratchpad)
Date Tue, 30 Mar 2004 09:44:21 GMT
Le 30 mars 04, à 11:19, Joerg Heinicke a écrit :

> ...IMO having blocks disabled is not a problem. But the way 
> re-enabling them is. It's no longer possible to tell the user "copy 
> blocks.properties to local.blocks.properties and edit this one". I 
> already had this issue when only including woody block after 
> deprecation....

Because the current detection is based on the presence of the 
"exclude.block.xyz" rather than its value, is that right?

> ...So when doing it - what it is a good thing - we have to change the 
> build process in relation to blocks selection. Isn't it possible to 
> switch to include.block.{blockname}={true|false} syntax...

I'd be +1 on this, "include.block.xyz" makes more sense.

-Bertrand


Mime
View raw message