On Tue, 2007-07-10 at 23:03 -0700, Ralph Goers wrote:
I checked out the latest and ran mvn -Dmaven.test.skip=true -P allblocks
install on Windows using Maven 2.0.6 and Java 1.6.0_01. Any ideas?
Missing:
--
1) org.apache.cocoon:cocoon-rcl-webapp-wrapper:jar:1.0.0-RC1-SNAPSHOT
Date: Tue, 10 Jul 2007 23:03:27 -0700
From: [EMAIL PROTECTED]
I checked out the latest and ran mvn -Dmaven.test.skip=true -P allblocks
install on Windows using Maven 2.0.6 and Java 1.6.0_01. Any ideas?
Given Carsten's reply in the 2.2 does not build with JDK1.4.2 thread, have
you tried
Andrew Stevens wrote:
Date: Tue, 10 Jul 2007 23:03:27 -0700
From: [EMAIL PROTECTED]
I checked out the latest and ran mvn -Dmaven.test.skip=true -P allblocks
install on Windows using Maven 2.0.6 and Java 1.6.0_01. Any ideas?
Given Carsten's reply in the 2.2 does not build with JDK1.4.2
Andrew Stevens ats37 at hotmail.com writes:
The problem in that other thread was also that Maven 2.0.6
resolved a dependency differently in different JDK versions.
That's a kind of funny. Now Maven tells us what our JDK has to be ;-)
Is that a problem of a particular POM? Can they specify if
Bart Molenkamp wrote:
Anyone any idea?
yes, my fault :-(
At the weekend I upgraded to the latest version of commons-jci which is only
available from SVN but not in any public Maven repo.
For now I commented both rcl modules in cocoon/trunk/tools/pom.xml. There could
be some references in
The problem is that the cocoon-pipeline-impl TEST-jar is missing.
Test-jars are built in the test step, ie. -Dmaven.test.skip=true is
*not* set. Normally only other test-jars depend on such a test-jar (e.g.
when you have a Test base class, which is the case in cocoon, although I
am not
