View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060502004754
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-3.2-testsuite?log=log20060502024157
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060502033347
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:41: Exit code: 1 See compilejbosshead.log in Build Artifacts
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060502041407
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:132: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060502041839
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:75: Exit code: 1 See tests.log in Build Artifacts for details.Date of
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossws-testsuite?log=log20060502044913
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
When JBossXB, common, test and aop are properly standalone.
I've still not seen something I can manage in this respect.
Cache, Remoting, Webservices maybe happy to run before they can walk,
I am not.
On Mon, 2006-05-01 at 08:44 -0500, Scott M Stark wrote:
The mc code should be pulled out of
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060502034240
TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line:
JBossPOJOServer-1.0 Alpha / Final
Can those releases be removed from JIRA? There is just one open issue
recorded (http://jira.jboss.com/jira/browse/JBAS-2545) that should
probably move to JB5, if not there already.
Thanks
/D
---
Using Tomcat
Yes.
On Tue, 2006-05-02 at 06:13 -0500, Dimitris Andreadis wrote:
JBossPOJOServer-1.0 Alpha / Final
Can those releases be removed from JIRA? There is just one open issue
recorded (http://jira.jboss.com/jira/browse/JBAS-2545) that should
probably move to JB5, if not there already.
Thanks
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-serialization-testsuite?log=log20060502052010
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:05/02/2006 05:20:10Time to build:Last changed:05/02/2006 01:32:07Last log entry:Fixing setClassLoader option
Can we create an svn equivalent to this cvs repository info page:
http://wiki.jboss.org/wiki/Wiki.jsp?page=CVSRepository
Scott Stark
VP Architecture Technology
JBoss Inc.
---
Using
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-sybase-testsuite?log=log20060502074204
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:107: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-db2-testsuite?log=log20060502074255
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:116: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-mssql-testsuite?log=log20060502074348
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:123: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060502075853
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:75: Exit code: 1 See tests.log in Build Artifacts for details.Date of
Then either head should be moved to svn so that project refactoring can
be done with history maintained, or these modules be removed from
jboss-head and reintegrated as binary dependencies so that they can be
migrated seperately.
I doubt a complete move is practical given the J1, JBW timeline
Which of this is the showstopper?
http://jira.jboss.com/jira/browse/JBBUILD-307
The issue for me is being able to develop against the
HEAD/Snapshot of each dependent project without creating an infinite
number of versions in the repository. :-)
e.g. the ongoing integration between AOP/MC
require
JBBUILD-307 subtasks:
2. Create script to modify a SVN jbossas repo and change the
directories to the proper names is certainly a show stopper as the
migration of the cvs modules does not honor the cvs module aliases. The
jboss-head or jboss-4.0.x tag/branch from cvs contains the raw cvs
module
On Tue, 2006-05-02 at 09:07 -0500, Scott M Stark wrote:
It would potentially be possible to require the MC projects
to be developed against head while still being thirdparty
binaries in the main jboss-head build.
i.e. You would checkout the projects separately into the head tree.
Ok, I'll do this. If you want to use JDK5 features, we should
also look at make jboss retro binaries.
Yes, I do so we need separate binaries for 14.
I'll make JBoss-Head build on the JBossMC-1.0.2.GA binaries.
Besides the bean deployer in varia, only EJB3 is using it
until
For the 42 open 4.0.4.GA issues:
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=truemode=hi
desorter/order=DESCsorter/field=priorityresolutionIds=-1pid=10030fi
xfor=12310691
These either need to be in progress this week and done by Monday the 8th
or they will be postponed. Dimitris
Ok, then we just need to define a cutoff date for the common module to
be frozen in head and then remove the module from jboss-head and switch
to binary imports. Alexey I don't see any cvs commits to jbossxb
recently, are you already working off of the svn repo?
-Original Message-
From:
The first problem I've come across is that AOP is using the container
project for the metadata repository interfaces.
There is no binary release of this yet,
since it is still being developed.
So how doable is this while we are still working on the AOP/MC
integration with still unstable apis?
We have to bootstrap the repository with a snapshot version. This can be
a local jbossbuild repository override to avoid having to synch through
cvs and then out to the webserver.
It's the same problem we will face when developing multiple maven
projects with inter-dependencies. Maven just has a
This is the use case which Maven enables especially well, no?
ie, update code in container, build it, and then test the impact in AOP.
The jars from container are integrated into the AOP build using Maven's
local repository. There is no update the repository step since it is
part of the default
On Tue, 2006-05-02 at 11:54 -0500, Scott M Stark wrote:
We have to bootstrap the repository with a snapshot version. This can be
a local jbossbuild repository override to avoid having to synch through
cvs and then out to the webserver.
Can you explain how this works?
I can put a snapshot of
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060502101543
TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line:
Correct.
-Original Message-
From: Ryan Campbell
Sent: Tuesday, May 02, 2006 10:12 AM
To: Scott M Stark; Adrian Brock
Cc: QA; 'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-head-jdk-matrix Build Failed
This is the use case which Maven enables especially well, no?
Right. And if you were to be to be in heavy development mode, rather
than publishing a number of different versions, you would just publish
snapshots to the public repository. This eliminates the need to create
a buttload of versions.
Ruel Loehr
JBoss QA
-
With jbossbuild we have to do the rebuild snapshot step manually because
its not supported by the build. With maven you could pull all of these
projects together with the dependcies and missing/out of date binaries
will be built. You could convert these projects to use maven first to
achieve this.
If container depended on aop and aop was not yet built and had not yet
published any binary artifacts, the build of course, would fail. This
is assuming that both of these were standalone projects. If they were
contained under the same parent build maven would look first for the
built artifacts
What do you guys think of this:
http://linuxintegrators.com/acoliver/code/2006/05/02/x-242.html
-andy
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to
This has been done, except the cruisecontrol changes.
I've left some other issues open for a more complete standalone build:
http://jira.jboss.com/jira/browse/JBMICROCONT-87
The updated build instructions are here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMicrocontainer
if you already have a
Yes.
http://wiki.jboss.org/wiki/Wiki.jsp?page=SVNRepository
Ruel Loehr
JBoss QA
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent:
Scott M Stark wrote:
Ok, then we just need to define a cutoff date for the common module to
be frozen in head and then remove the module from jboss-head and switch
to binary imports. Alexey I don't see any cvs commits to jbossxb
recently, are you already working off of the svn repo?
No, I've
Will removing these modules from jboss-head prevent previous releases of
ejb3, aop microcontainer from being built?
I guess the answer is no, but the checkout instructions have changed?
-Original Message-
From: Adrian Brock
Sent: Tuesday, May 02, 2006 2:21 PM
To: Scott M Stark
Cc:
You will just need to checkout the container/dependency/kernel projects
manually (they are no longer a part of the jboss-head alias).
Using whatever tag was added for that release.
Other than that, it will be the same.
It shouldn't affect AOP. Only AOP2.0 (which hasn't been released yet)
has a
Are the container and kernel modules jboss-container
jboss-microkernel as explained in the checkout instructions in the
wiki, or are they just container microkernel
-Original Message-
From: Adrian Brock
Sent: Tuesday, May 02, 2006 4:37 PM
To: Ryan Campbell
Cc: Adrian Brock; Scott M
You just rename them using the -d option when checking them out. So the
actual cvs modules use the jboss- prefix while the local directories
do not.
-Original Message-
From: Rajesh Rajasekaran
Sent: Tuesday, May 02, 2006 4:42 PM
To: Adrian Brock; Ryan Campbell
Cc: Scott M Stark; QA;
Yes, they container and microkernel in CVS.
Cut and paste error, sorry.
On Tue, 2006-05-02 at 16:42 -0500, Rajesh Rajasekaran wrote:
Are the container and kernel modules jboss-container
jboss-microkernel as explained in the checkout instructions in the
wiki, or are they just container
No, it doesn't.
We plan to reduce the lag on the repository updates, which should reduce
our exposure to this problem.
-Original Message-
From: Adrian Brock
Sent: Tuesday, May 02, 2006 4:45 PM
To: QA
Cc: Adrian Brock; Bill Burke; Brian Stansberry; Clebert Suconic;
Dimitris Andreadis;
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-hsqldb-testsuite?log=log20060502220010
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:85: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-mysql-testsuite?log=log20060502220116
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:92: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-oracle-testsuite?log=log20060502220220
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:100: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060502220006Lbuild.55
BUILD COMPLETE-build.55Date of build:05/02/2006 22:00:06Time to build:24 minutes 34 seconds
Unit Tests: (0) Total Errors and
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060502220252
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:72: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-mssql-testsuite?log=log20060503011930
BUILD FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:123: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-serialization-testsuite?log=log20060502234028
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:05/02/2006 23:40:28Time to build:Last changed:05/02/2006 16:21:36Last log entry:JBSER-71 - removing unused variable
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060503014828Lbuild.49
BUILD COMPLETE-build.49Date of build:05/03/2006 01:48:28Time to build:3 minutes 49 secondsLast changed:05/02/2006 12:56:04Last log entry:refactorings
50 matches
Mail list logo
