Reinhard Poetz wrote: > Today, Jorg and I had a long chat about this. In short, we failed to > find a solution that works with Maven 2 as it is today. The problem is > that Cocoon block requirements have a different purpose than Maven 2 > dependencies. Cocoon block requirements desribe what a block needs to > run while Maven 2 dependencies describe what a project needs to compile. > Additionally we want to describe our dependencies as contracts and not > as direct dependencies to a JAR. >
how is that different? I would guess this just means your 'contract' is available in a separate jar/artifact from your implementation? is that a constraint that is hard to keep up with? -marc= (only taking first steps in the maven/block work, so seeking no more then understanding) -- Marc Portier http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/mpo/ [EMAIL PROTECTED] [EMAIL PROTECTED]
