On Sep 23, 2009, at 2:50 PM, Dominic Mitchell wrote:
On Wed, Sep 23, 2009 at 7:44 PM, Steven D. Majewski <[email protected]
> wrote:
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending on the
other?
Did you also add the dependency of myblock2 in the pom.xml of
myblock1?
Yes. ( And if I take that dependency out, it runs without complaint. )
I'm guessing that is happening by accident. If you run "mvn clean"
it'll stop working.
[ with myBlock2 installed ]
cd myBlock1
mvn clean
mvn jetty:run
with that myBlock2 dependecy commented out:
http://localhost:8888/myBlock1/
http://localhost:8888/myBlock2/
http://localhost:8888/myBlock1/callingBlock2
all work.
The reason is that Cocoon extracts blocks into a "work" directory
when it starts up. When you run through maven with "jetty:run",
that's in target/work. "mvn clean" removes the target/ directory,
so it'll probably stop it from working.
-Dom
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
