This is still occurring for me ..
Is anyone else seeing this??
Ovidiu Feodorov wrote:
The 796th reason to switch to a separated build ...
Tim Fox wrote:
I'm getting the following after doing a cvs update -C in HEAD and then a
build clean:
BUILD FAILED
My jbossxb is currently at snapshot not 1.0.0.CR4
but then I'm trying to avoid resynching with head too
often to avoid all the build breakages. :-)
On Mon, 2006-06-26 at 08:55 +0100, Tim Fox wrote:
This is still occurring for me ..
Is anyone else seeing this??
Ovidiu Feodorov wrote:
Maybe you changed the local filesystem date?
Try deleting the directory from thirdparty.
On Mon, 2006-06-26 at 10:34 +0200, Adrian Brock wrote:
My jbossxb is currently at snapshot not 1.0.0.CR4
but then I'm trying to avoid resynching with head too
often to avoid all the build breakages. :-)
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060626023311
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-compatibility-matrix?log=log20060626060744Lbuild.34
BUILD COMPLETE-build.34Date of build:06/26/2006 06:07:44Time to build:32 minutes 10 secondsLast changed:06/24/2006 20:59:15Last log
No. Except for writing a DataHandler abstraction that WS project would
have to implement.
Copying to the jboss-dev, maybe others will have better suggestions.
Heiko Braun wrote:
Hi Alex,
do you have an idea how we could solve
http://jira.jboss.com/jira/browse/JBWS-995 without
a)
Thx, that worked.
Adrian Brock wrote:
Maybe you changed the local filesystem date?
Try deleting the directory from thirdparty.
On Mon, 2006-06-26 at 10:34 +0200, Adrian Brock wrote:
My jbossxb is currently at snapshot not 1.0.0.CR4
but then I'm trying to avoid resynching with head too
Of course the build is still broken for other reasons
I wonder if anyone's going to take a look at that anytime soon (JDK5
apache naming jar incompatibility) ?
It's *definitely* time to move off HEAD and on to labs. :)
Refreshing from HEAD is just too much of a lottery IMHO - you might be
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite-140?log=log20060626081926
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line:
So, head should only be compilable with a 1.5 jdk.
However, some modules will still enforce source target at 1.4, so
that
we can back merge fixes to the jboss4 tree.
Correct?
What's the latest on this? The JSF integration code under the Tomcat
module needs JDK 1.5 to compile. I can
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060626095914Lbuild.146
BUILD COMPLETE-build.146Date of build:06/26/2006 09:59:14Time to build:60 minutes 39 secondsLast changed:06/26/2006 04:57:29Last log
Tomcat6/jbossweb bundled in jboss5 will require jdk5.
-Original Message-
From: Stan Silvert
Sent: Monday, June 26, 2006 8:04 AM
To: Ryan Campbell; 'JBoss.org development list'; Scott M Stark
Cc: The Core; Bill Burke
Subject: RE: [JBoss-dev] Tomcat 6 integrated
So, head should only be
1.5 is a pain for us, since we need to build and test our (jboss
messaging) releases using 1.4
Stan Silvert wrote:
So, head should only be compilable with a 1.5 jdk.
However, some modules will still enforce source target at 1.4, so
that
we can back merge fixes to the jboss4 tree.
Jboss5 requires a java5 runtime due to javaee5 requirements so you need
to get off of head.
-Original Message-
From: Tim Fox
Sent: Monday, June 26, 2006 8:09 AM
To: Stan Silvert
Cc: Ryan Campbell; JBoss.org development list; Scott M Stark; The Core;
Bill Burke
Subject: Re: [JBoss-dev]
Our migration to labs is due to happen (very) soon...
In the mean-time we can just edit out the tomcat from the build since we
don't have any dependencies on it.
Scott M Stark wrote:
Jboss5 requires a java5 runtime due to javaee5 requirements so you need
to get off of head.
-Original
Anybody have a problem with hard-coding 1.5 in the Tomcat build.xml
until we can get the other stuff out of head?
Or, can we go ahead and change it for the whole build?
Stan Silvert
JBoss, a division of RedHat
[EMAIL PROTECTED]
-Original Message-
From: Scott M Stark
Sent: Monday,
We won't change it for the whole build. Some modules are required to be built
to a 1.4 specification so that we can backport changes if necessary.
The required changes at this point are:
1) Up the src target version of tomcat to 1.5
2) Modify cruisecontrol to build jboss-head with a 1.5 jdk
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060626110417
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060626133415
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-compatibility-matrix?log=log20060626180812
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:249: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060626195309
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:287: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuite?log=log20060626212120
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-portal.xml:47: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060626214139Lbuild.1936
BUILD COMPLETE-build.1936Date of build:06/26/2006 21:41:39Time to build:40 minutes 26 secondsLast changed:06/26/2006 20:43:26Last log entry:updated the
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060626215956Lbuild.102
BUILD COMPLETE-build.102Date of build:06/26/2006 21:59:56Time to build:35 minutes 58 seconds
Unit Tests: (0) Total Errors and
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb-windows?log=log20060626223604Lbuild.36
BUILD COMPLETE-build.36Date of build:06/26/2006 22:36:04Time to build:46 minutes 19 seconds
Unit Tests: (0) Total Errors
I see similar issues. I just updated the jbossmc checkout which includes
the container project. I'm seeing the following error in the Problems
panel:
SeverityDescription ResourceIn Folder Location
Creation Time
2 Project container is missing required library:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060627000110
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line:
27 matches
Mail list logo
