cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Savory <and...@luminas.co.uk>
Subject Re: 2.2 failing to build: cocoon-javaflow
Date Mon, 16 Apr 2007 11:33:50 GMT
Hi,

On 16 Apr 2007, at 12:05, Reinhard Poetz wrote:

> In short, add the commons-jci dependency to the javaflow block  
> only. I don't know if the javaflow-interpreter works then (I guess  
> not) but at least it should fix your build problems.

Ok, I've added it there and it seems to allow the build to succeed.  
Can others more informed on javaflow check there's no problems?

Index: blocks/cocoon-javaflow/cocoon-javaflow-impl/pom.xml
===================================================================
--- blocks/cocoon-javaflow/cocoon-javaflow-impl/pom.xml (revision  
529180)
+++ blocks/cocoon-javaflow/cocoon-javaflow-impl/pom.xml (working copy)
@@ -77,5 +77,10 @@
        <artifactId>commons-jci-fam</artifactId>
        <version>1.0-SNAPSHOT</version>
      </dependency>
+    <dependency>
+      <groupId>org.apache.commons</groupId>
+      <artifactId>commons-jci-core</artifactId>
+      <version>1.0-RC1</version>
+    </dependency>
    </dependencies>
</project>


>> Also, I'm slightly mystified that I seem to be the only one  
>> hitting this. Is no-one else building 2.2?
>
> I guess that others who are building 2.2 got the dependency added  
> to the local repos because of building the reloading classloader  
> plugin (trunk/tools/cocoon-rcl) but this is really strange because  
> cocoon-rcl hasn't been added to the default build AFAIK.

<rant>
This has been bugging me for a long time. It used to be the case that  
people would do clean compiles against clean copies of Cocoon to make  
sure their changes wouldn't impact others (by causing the build to  
fail, for example). Has the move to Maven stopped this from being  
possible? Are people just not bothered about making sure trunk always  
builds?
</rant>

Should we come up with some sort of 'community guideline' saying that  
we should clear out our maven repository and do a clean build before  
committing? One person having to go through the loop of downloading  
and building everything clean is a small price to pay when you  
consider how many people's time could be wasted otherwise. Or is  
there something else we can do to prevent the continual pain of  
"BUILD FAILED" ?


Thanks,

Andrew.
--
Andrew Savory, Managing Director, Sourcesense UK
Tel: +44 (0)870 741 6658  Fax: +44 (0)700 598 1135
Web: http://www.sourcesense.com/



Mime
View raw message