View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060209064756
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/concurrent-testsuite?log=log20060209102227
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-concurrent-testsuite.xml:73: The following error occurred while executing this line:
So after listening to the Maven2 webinar yesterday and talking with
Ryan, Ruel and Steve E as a lead, I don't see a good reason why we
shouldn't look to using maven2 as the core of the jbossbuild. The two
outstanding proof of concept issues I asked Ruel to look at are:
1. Source in the
I've put a Maven contributor and evangelist in copy. Maybe Tim can also
facilitate us getting involved with the project at Apache.
Scott M Stark wrote:
So after listening to the Maven2 webinar yesterday and talking with
Ryan, Ruel and Steve E as a lead, I don't see a good reason why we
The problem I don't see addressed (and the main reason why I started
the jbossbuild prototype) is to have a top level which includes
multiple projects.
e.g. I wanted people to be able to do something like:
build
component name=JBossAS download=binary quality=LastGoodTests
component
Great.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Bill Burke
Sent: Thursday, February 09, 2006 7:54 AM
To: jboss-development@lists.sourceforge.net; Tim O'Brien
Subject: Re: [JBoss-dev] On the edge of the Maven cliff
I've put a Maven
So this is item 3 on Ruel's list to look into. It's related to item 1.
as I explained its usage to Ruel.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Adrian Brock
Sent: Thursday, February 09, 2006 8:14 AM
To:
That would kick ass...
Still, I think we should become Maven contributors and extend Maven to
do this.
Adrian Brock wrote:
The problem I don't see addressed (and the main reason why I started
the jbossbuild prototype) is to have a top level which includes
multiple projects.
e.g. I wanted
Yes, leveraging a community of people interested in builds vs jboss
resources makes more sense.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Bill Burke
Sent: Thursday, February 09, 2006 8:21 AM
To: jboss-development@lists.sourceforge.net
I just fixed this. It was failing due to
the changes in the compatibility matrix tests, sorry.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 08, 2006
11:05 PM
To: Andy Oliver; Adrian Brock; Alexey Loubyansky; Anil Saldhana; Bill Decoste; Bela Ban;
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060209221311
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
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060210005407
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-JBossCache.xml:96: The following error occurred while executing this line:
12 matches
Mail list logo