View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060623004551
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:72: The following error occurred while executing this line: /services/
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log2006064724Lbuild.98
BUILD COMPLETE - build.98Date of build: 06/22/2006 22:47:24Time to build: 35 minutes 45 seconds
Unit Tests: (0) Total Errors an
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-compatibility-matrix?log=log2006061517Lbuild.28
BUILD COMPLETE - build.28Date of build: 06/22/2006 22:15:17Time to build: 53 minutes 59 secondsLast changed: 06/22/2006 16:12:46Last log entry: JBBU
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb-windows?log=log20060622215953Lbuild.32
BUILD COMPLETE - build.32Date of build: 06/22/2006 21:59:53Time to build: 47 minutes 20 seconds
Unit Tests: (0) Total E
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060622182958
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622211038
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossws-testsuite?log=log20060622204850
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jbossws-testsuite.xml:41: Exit code: 1 See compilejbossws.log in Build Artifacts for details.Date of build
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuite?log=log20060622202524Lbuild.5
BUILD COMPLETE - build.5Date of build: 06/22/2006 20:25:24Time to build: 22 minutes 32 secondsLast changed: 06/22/2006 19:29:03Last log entry: adding/rem
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622194305
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622180832
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060622171529
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-serialization-testsuite?log=log20060622161132Lbuild.9
BUILD COMPLETE - build.9Date of build: 06/22/2006 16:11:32Time to build: 54 minutes 32 secondsLast changed: 06/20/2006 20:02:43Last log entry: Fixing
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622161129
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
This work has been completed.
Both head and the 4.0 branch are now building against the binary common
artifacts rather than the cvs source.
The svn repository is also now available for use. Development should take
place here from this point forward.
http://wiki.jboss.org/wiki/Wiki.jsp?page=J
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-compatibility-matrix?log=log20060622152903
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:272: The following error occurred while executing this line: /services/cruisecontrol/w
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-compatibility-matrix?log=log20060622144401
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:238: The following error occurred while executing this line: /services/cruisecontrol/w
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622141431
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060622143712
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:132: The following error occurred while executing this line: /services/cruisecontrol/wor
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060622133712
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:175: The following error occurred while executing this line: /services
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060622120812
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622125721
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622115158
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
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?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Anil Saldhana
Sent: Thursday,
I've updated the tests to use
org.jboss.web.tomcat.tc6.session.AopMarker. The build complains about
not being able to find testsuite\src\resources\cluster\http\jboss-aop.xml, but
at least it builds now.
From: Kabir KhanSent: Thu 6/22/06
11:10To: jboss-development@lists.sourceforge.netCc: B
Ruel is looking into this. The issue is that the Tomcat jars need JDK5
for compilation and the way the current HEAD build is setup, we may have
some issues.
Scott M Stark wrote:
> The tomcat module needs jdk5, not all of head. jboss5 will require a
> jdk5 runtime.
>
>
>> -Original Messa
On 6/22/06, Scott M Stark <[EMAIL PROTECTED]> wrote:
> Ok, I thought Mladen said the deployer was replicated currently. Yes, we need
> to be able to move at our own pace for the web container and I view that the
> jbossweb project should be the exchange point between tomcat and jbossas.
>
Maybe
Ok, I thought Mladen said the deployer was replicated currently. Yes, we need
to be able to move at our own pace for the web container and I view that the
jbossweb project should be the exchange point between tomcat and jbossas.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[
On 6/22/06, Scott M Stark <[EMAIL PROTECTED]> wrote:
> We should by synching on a release version of jbossweb in the future. It
> makes little sense to me to have jbossweb as a standalone web container
> and not bundle it in the AS. I talked to Mladen about breaking up the
> existing jbossweb proje
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622103421
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
The tomcat module needs jdk5, not all of head. jboss5 will require a
jdk5 runtime.
> -Original Message-
> From: Anil Saldhana
> Sent: Thursday, June 22, 2006 8:06 AM
> To: JBoss.org development list
> Cc: Bill Burke; The Core
> Subject: Re: [JBoss-dev] Tomcat 6 integrated
>
> Hi Scott,
We should by synching on a release version of jbossweb in the future. It
makes little sense to me to have jbossweb as a standalone web container
and not bundle it in the AS. I talked to Mladen about breaking up the
existing jbossweb project to move its duplicated deployer code into the
AS project.
The problem seens to be that the tc5.AopMarker is no longer on the classpath.
The tc6-cluster.aop file contains tc5.AopMarker, and also does not contain the
InstanceAopMarker .
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On
> Behalf Of Adrian Brock
> Sen
This is temporary until Tomcat6 is released.
Dimitris Andreadis wrote:
>>So at the end of the day, the Tomcat code in JBoss will not
>>exactly correspond to an official Tomcat release version. Is
>>that correct?
>>
>>I know we have been maintaining full Tomcat source within the
>>JBoss AS CVS.
Hi Scott,
with regard to the current TC6 integration that Bill undertook in HEAD:
http://jira.jboss.com/jira/browse/JBAS-3330
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85382
This has placed a need for JDK5 in HEAD as TC6 needs it.
You will need to
> So at the end of the day, the Tomcat code in JBoss will not
> exactly correspond to an official Tomcat release version. Is
> that correct?
>
> I know we have been maintaining full Tomcat source within the
> JBoss AS CVS. I'm wondering about the pros and cons you
> experienced with Tomcat b
So at the end of the day, the Tomcat code in JBoss will not exactly
correspond to an official Tomcat release version. Is that correct?
I know we have been maintaining full Tomcat source within the JBoss AS
CVS. I'm wondering about the pros and cons you experienced with Tomcat
because I'm not sur
One of the recent changes (aop or web sessions) has broken
the testsuite build...
[copy] Copying 1 file
to
/home/ejort/jboss-head/testsuite/output/resources/cluster/http/http-scoped/WEB-INF
[war] Building
war: /home/ejort/jboss-head/testsuite/output/lib/http-scoped-set-attr.war
Overrid
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622063520
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060622051505
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:223: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
I suppose the 'common' sources will be removed
from Branch_4_0 & HEAD ?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Ruel LoehrSent: 21 June, 2006 23:30To:
jboss-developmentSubject: [JBoss-dev] Promotion of common module to
independent project
T
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060622022314
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:238: The following error occurred while executing this line: /services/cruisecontrol/work/scripts
41 matches
Mail list logo
