Hi Torsten, after having another close look at my cocoon 2.2 trunk build, I could see, that the build of "allBlocks" was successful, but the javaFlow block was not build because of the missing dependency you were talking about. I think it's really great, that we have to use Maven to get rid of dependency problems ... Looking forward to Maven3 ;-)
Do I really have to build Commons myself now? ... I have to admit that the struggle of getting C2.2 to work is sort of really pissing me off. I think this even higher initial learning curve will keep more and more users from using Cocoon. Instead of getting easier it's getting more and more complicated :-( ... I want my Ant build back! ;-) Chris -----Ursprüngliche Nachricht----- Von: Torsten Curdt [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 14. August 2008 10:57 An: [email protected] Betreff: Re: AW: JavaFlow in Cocoon 2.2 I suspect the problem to be that the commons-javaflow snapshot got pruned from the repository. But that's just a guess. Use maven with verbose output. It should tell you. cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
