Hi: I think it is a good idea to talk about the "protocol to add new blocks", but currently there is no an avalanche or an "invasion" of new blocks. :-(
As suggested the solution can be that every block can have his own build.xml and just integrate it by extending a "main" build.xml. I am not sure if this the old way. I also remember Stefano rewrote the build system because it was too slow. In fact, I am be glad to see Cocoon reaching new areas in form of optional features called blocks. Best Regards, Antonio Gallardo. Upayavira dijo: > Carsten Ziegeler wrote: > >>Bertrand Delacretaz wrote: >> >> >>>I don't think it would be very hard to make the blocks system >>>more configurable, so that external blocks would need only an >>>XML descriptor to be integrated at compile-time. But someone >>>has to do it. >>> >>> >>> >>I always thought about simply adding all blocks that are in >>the src/blocks/local directory (like we do with libs in >>lib/local). But I don't know what effort this requires, but >>it shouldn't be too hard. >> >> > And use an Ant property to specify this location, so that you can point > to blocks which are outside the Cocoon hierarchy. > > Upayavira > >
