Jorg Heymans wrote:
Joerg Heinicke wrote:
Eeeeh, I hope not! I'd worry about the health of the overall
codebase if
no-one else is building allblocks! Is this why continuum is not failing
when it should be?
...
I can only agree with Andrew. The goal has to be that all blocks are
Joerg Heinicke wrote:
Eeeeh, I hope not! I'd worry about the health of the overall codebase if
no-one else is building allblocks! Is this why continuum is not failing
when it should be?
...
I can only agree with Andrew. The goal has to be that all blocks are
working and continuum runs all
Hi,
On 16 Apr 2007, at 21:00, Grzegorz Kossakowski wrote:
I run mvn install with clean (actually, temporary) repository from
time to time and do not experience problems you outlined. However,
I do
not build with -Pallblocks option and that's probably the difference.
From what I understand,
Andrew Savory napisał(a):
Hi,
Eeeeh, I hope not! I'd worry about the health of the overall codebase if
no-one else is building allblocks! Is this why continuum is not failing
when it should be?
My opinion is that we should view situation with blocks in more blockish way.
Blocks in C2.2
On 17.04.2007 16:25, Grzegorz Kossakowski wrote:
Eeeeh, I hope not! I'd worry about the health of the overall codebase if
no-one else is building allblocks! Is this why continuum is not failing
when it should be?
My opinion is that we should view situation with blocks in more blockish way.
Hi,
Trying to do a clean build of C2.2 I'm seeing errors building cocoon-
javaflow because of a missing org.apache.commons:commons-jci-core:jar:
1.0-RC1.
jci-core 1.0-SNAPSHOT seems to be commented out of cocoon-core. The
below fixes it and allows c2.2 to build, but as I don't know what it
Andrew Savory wrote:
Hi,
Trying to do a clean build of C2.2 I'm seeing errors building
cocoon-javaflow because of a missing
org.apache.commons:commons-jci-core:jar:1.0-RC1.
jci-core 1.0-SNAPSHOT seems to be commented out of cocoon-core. The
below fixes it and allows c2.2 to build, but as I
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
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?
I haven't checked javaflow against the RC1 of jci yet
Index: blocks/cocoon-javaflow/cocoon-javaflow-impl/pom.xml
Andrew Savory wrote:
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
Marc Portier wrote:
now, to solve things I think we better
- ask jci peeps to publish non-snapshot releases on a public repo (this
includes RC-releases)
- or just add my patch to the pom, rather then yours, no?
oh, upon reread I think additional clarification is due:
our patches do
Andrew Savory napisał(a):
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
12 matches
Mail list logo
