OK. It works properly if I create a new block.
Does this mean that it is not always possible to add a dependency to a block
without matching the version to the state of the trunk at the time it was
created?
Is this more a Maven issue than Cocoon? What happens when the dependency
tree contains
On 10.05.2005 22:09, Silvela, Jaime (Exchange) wrote:
I've just started using Cocoon 2.1.7 and have to port to it a website
that was built using 2.1.6
I can build the website just fine, but when I go to it from my browser,
it complains Could not load class
