View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060211003634
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details.Date of build: 02/11
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060210171839Lbuild.1393
BUILD COMPLETE - build.1393Date of build: 02/10/2006 17:18:39Time to build: 34 minutes 50 secondsLast changed: 02/10/2006 17:08:40Last log entry: fix build
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060210161905
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20060210150533
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:271: The following error occurred while executing this line: /services/cruisecontrol/work/script
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/concurrent-testsuite?log=log20060210142339
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-concurrent-testsuite.xml:73: The following error occurred while executing this line: /services/cruisecontrol/work
Let's do that. Do you want to couple this to maven? It would help Ruel I
suppose.
> -Original Message-
> From: Adrian Brock
> Sent: Friday, February 10, 2006 9:34 AM
> To: Scott M Stark
> Cc: jboss-development@lists.sourceforge.net; QA
> Subject: RE: Ongoing build changes: was RE: [JBoss
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20060210115431
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:271: The following error occurred while executing this line: /services/cruisecontrol/work/script
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060210100340
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
As for me, we've got to the point when this is a priority.
I want to make XB a standalone project ASAP but am not sure how.
It depends on JBoss logging at least. Probably, we should define
independent projects like, hopefully, the logging and make them
standalone first?
Scott M Stark wrote:
So we need to carve out a "minimal" impact strategy considering projects
that today are tied to the jbossas head cvs structure. Maybe we need a
nightly snapshot of jbossas in the repository with redefinition of
projects like ejb3 to decouple them during the transition.
> -Original Message-
FYI, we already do this for AOP.
Adrian Brock wrote:
On a related issue. I really want to bite the bullet
on sorting out the jboss-common dependencies and making more
managable chuncks for standalone projects to eat.
I've been waiting for the ongoing build changes to stabalise
before doing this
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060210091944
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
I'm not following. aop and xb are no brainer standalone projects that
should not be in the jbossas cvs module alias by default. ws and ejb3
probably need to be refactored into standalone modules and a server
integration module which can be included in jbossas.
I'm not advocating chaos in head bec
Part of the problem is everyone running around trying to get work done
on multiple branches while Ruel is trying to baby step new build setups
in. I think we need to get to a point where we just say head is going to
be refactored and potentially broken for an extended period of time
while we refact
We already have a task for it
http://jira.jboss.com/jira/browse/JBBUILD-58
But I don't believe anybody has really looked at what it will
take in general.
My comments on the issue in the forums are mainly based
on what I remember seeing when I was fixing other things.
None of the JIRA tasks conta
I don't see stabilization happening though as we still have the pending
maven move and restructing to have a common module structure and
potentially splitting up existing projects to better match the maven
ideal. Let's just define how we want commons broken up with Ruel in the
loop so he can chase
On a related issue. I really want to bite the bullet
on sorting out the jboss-common dependencies and making more
managable chuncks for standalone projects to eat.
I've been waiting for the ongoing build changes to stabalise
before doing this in jboss-head.
This would allow us to properly have on
17 matches
Mail list logo
