??? This is really weird... That would mean that somehow the myBlock2.jar is in the classpath of myBlock1... the only possible explanation I can think of is that you configured this dependency in the rcl file...
But if you were to package the war file without that dependency I'm 99% sure this will not work anymore. So don't think you're there yet ;-) Robby -----Original Message----- From: Steven D. Majewski [mailto:[email protected]] Sent: Wednesday, September 23, 2009 8:58 PM To: [email protected] Subject: Re: problems with "Getting Started" 2.2 [was: Starting out with Cocoon 2.2] 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
