Just do a 4.0.5 soon after than. I don't want to push the 4.0.4.GA as
Dimitris said people have been waiting on it for a while.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Monday, March 20, 2006 6:54 PM
To: jboss-development@lists.sour
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060321002641
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060320223436Lbuild.44
BUILD COMPLETE - build.44Date of build: 03/20/2006 22:34:36Time to build: 35 minutes 5 secondsLast changed: 03/20/2006 12:35:16Last log entry: updated releas
let me know if any issues come up. The backmerge has been completed.
--
Bill Burke
Chief Architect
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media.
It would be cool if we could push GA a bit further after CR2. I would
like to do a big push for EJB3 final draft(and my book) compliance with
4.0.4 and need more than 2 weeks as I'm on vacation for 10 days in between.
Scott M Stark wrote:
Ok. We want the 4.0.4.CR2 out this week and the GA two
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060320181206
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts
Ok. We want the 4.0.4.CR2 out this week and the GA two weeks latter.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Steve Ebersole
> Sent: Monday, March 20, 2006 2:17 PM
> To: jboss-development@lists.sourceforge.net
> Subject: RE: [JBoss-dev] 4.
Looks like there is already a similar
issue logged against jboss-head…
http://jira.jboss.org/jira/browse/JBAS-2072
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Clebert Suconic
Sent: Monday, March 20, 2006 5:06
PM
To: jboss-development@lists.sourceforge.ne
I’m seeing this error when starting JBossProfiler with
JBoss-4.0 fresh install.
It works with any other previous version. Any idea on what
changed? (did we change any classLoader op here?)
18:01:48,986 ERROR [MainDeployer] Could not create
deployment:
file:/home/csuconic/jboss-4.
So provided we do not cause issues with portal, I say we go with a 3.2
final. Specific reasons:
(1) Less issues with the version differences between AS and EJB3
(2) JBossCache optimistic locking support (only in 3.2)
(3) Javassist support (only in 3.2)
(4) Some performance enhancements relating to
Well the other piece to the puzzle is the differences between that
Hibernate version you mentioned and 3.1.3. If the differences there are
drastic enough, then I see even more of an argument to move to 3.2 for
the AS bundle. Another thing to consider is portal (which AFAIK is
still the only other
Your input is a large factor as well since I don't really know how
different the hibernate 3.1rc2jboss version that was shipped with
4.0.3SP1 and the current version needed for ejb3. The first question, is
what do you want bundled in terms of stability/support?
If this is not what is needed for ej
I don't see these txtimer errors running the tests by
itself. I'll check the run logs to see if there is something
obvious.
[EMAIL PROTECTED] testsuite]$ run_tests.shant
-Dtest=org.jboss.test.txtimer.test.CreateCancelTestCase -Dnojars=t
-Djunit.timeout=180 -Djbosstest.cluster.node0=192
It is up to y'all. I am fine with cutting a 3.2 final and then
continuing HEAD development as 3.3. But the 3.2 release introduced some
fairly different behavior in terms of non-transactional access more
in-line with what is defined in the EJB3 spec. These changes are
stricter than what Hibernate
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060320142201Lbuild.1578
BUILD COMPLETE - build.1578Date of build: 03/20/2006 14:22:01Time to build: 28 minutes 2 secondsLast changed: 03/20/2006 13:03:40Last log entry: JBWS-719En
No arguments there. I would agree that keeping the file structure the
same initially makes sense.
The pom.xml for the testsuite would build all testsuite src as well as
creating the necessary jars for deployment.
During the testing a phase, a custom test plugin could for each series
of tes
It seems like ejb3 should only be brining in a latter hibernate
dependency via the installer and a custom build for testing. The
default/all should not be bumped up to track ejb3 issues to an untested
hibernate release.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROT
Sure, I do this also; but:
(1) I prefer not adding brand new features in a point release, if
possible.
(2) The query parser re-work represents a significant change in the
code-base, which I'd also prefer to not include in a point release.
Another option, I guess, is to cut a 3.2 final after this
Steve Ebersole wrote:
This goes back to the previous discussion sometime last week.
JBoss itself *should* keep bundling 3.1.x - preferably 3.1.3 as soon as
I release it today/tomorrow; that is the stable release cycle. But that
screws EJB3 for the previously mentioned reasons.
So what's
yeah, this seems to work, but does anybody know if there is a better way?
Bill Burke wrote:
I'm looking at how we do parsing and looking at
XmlFileLoader.LocalErrorHandler.
It looks like errors are ignored if the schema wasn't resolved. Is this
the way to do it?
Bill Burke wrote:
How do y
This goes back to the previous discussion sometime last week.
JBoss itself *should* keep bundling 3.1.x - preferably 3.1.3 as soon as
I release it today/tomorrow; that is the stable release cycle. But that
screws EJB3 for the previously mentioned reasons.
So what's the solution?
Here's the r
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060320121502
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts
Exactly. Something stable, that can be tested with 4.0.4.CR2 (which is
delayed until Friday 24th or Monday 27th max), that satisfies Bill, and
won't require an immediate 4.0.4.SP1 release for fixes :)
There are many-many people waiting for 4.0.4 for quite some time and we
are already delayed, so
Yep.
Ok, so I'll implement that one mentioned feature and cut alpha3 which we
can use in 4.0.4...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Monday, March 20, 2006 12:45 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [J
On Mon, 2006-03-20 at 13:38 -0500, Bill Burke wrote:
> Tell me something I don't already know. I want validation if there is a
> schema specified, no validation if there is not.
>
And no default attributes, etc.
> Adrian Brock wrote:
> > The element declaration is required (from your error mes
we just need something stable for hibernate in 4.0.4 GA.
Steve Ebersole wrote:
Well, its *possible* to have "a final" release whenever I want ;)
But at a bare minimum there is one more feature that EJB3 will require
which still needs to be implemented; and it is an ugly one. I need to
release
Well, its *possible* to have "a final" release whenever I want ;)
But at a bare minimum there is one more feature that EJB3 will require
which still needs to be implemented; and it is an ugly one. I need to
release 3.1.3 today/tomorrow (this needs to be done for reasons
extraneous to this discuss
Tell me something I don't already know. I want validation if there is a
schema specified, no validation if there is not.
Adrian Brock wrote:
The element declaration is required (from your error message)
http://www.w3.org/TR/xmlschema-1/#cvc-elt
and validation is required for minimal conforman
The element declaration is required (from your error message)
http://www.w3.org/TR/xmlschema-1/#cvc-elt
and validation is required for minimal conformance:
http://www.w3.org/TR/xmlschema-1/#concepts-conformance
On Mon, 2006-03-20 at 13:20 -0500, Bill Burke wrote:
> How do you set up xml parsing t
I'm looking at how we do parsing and looking at
XmlFileLoader.LocalErrorHandler.
It looks like errors are ignored if the schema wasn't resolved. Is this
the way to do it?
Bill Burke wrote:
How do you set up xml parsing to not validate if there is no schema
specified in the XML?
Caused by:
How do you set up xml parsing to not validate if there is no schema
specified in the XML?
Caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the
declaration of element 'persistence'.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
I love those dependencies ;)
Is it possible to have a final next week ?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Steve Ebersole
> Sent: 20 March, 2006 19:33
> To: jboss-development@lists.sourceforge.net
> Subject: RE: [JBoss-dev] 4.0.4
4.0.4CR2 is going to go out with 3.2.0alpha2 as next release of EJB3
requires it.
Steve Ebersole wrote:
No way I'll have a 3.2 final this week ;)
And it is not a simple matter of re-target for 4.0.5. EJB3 relies on
changes made in the current alphas of 3.2 due to the latest changes in
the spe
No way I'll have a 3.2 final this week ;)
And it is not a simple matter of re-target for 4.0.5. EJB3 relies on
changes made in the current alphas of 3.2 due to the latest changes in
the spec (specifically the joinTransaction() stuff)...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:
Since the CR2 is going to be on the order of a week late, the GA needs
to be pushed back a week to give at least 2 weeks for feedback. The week
of the 10th should be the new GA target.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Dimitris And
But you need to get your changes with 4.0.4.CR2 (due out this week) so
they get tested!
After CR2 you'll need to target 4.0.5
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Dimitris Andreadis
> Sent: 20 March, 2006 19:09
> To: jboss-developme
3rd April (give or take)
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Steve Ebersole
> Sent: 20 March, 2006 19:03
> To: jboss-development@lists.sourceforge.net
> Subject: [JBoss-dev] 4.0.4
>
> I am trying to nail down a short-term release s
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060320112913
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/
I am trying to nail down a short-term release schedule for Hibernate
3.2.x. Due to some of the changes made there specifically for EJB3
persistence support, I need to have a stable version of 3.2 done before
AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward.
Is there an anticipated relea
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060320103744
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-seam-testsuite?log=log20060320102614
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:54: /services/cruisecontrol/work/scripts/test-output not found.Date of build: 03/20/2006
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060320095930
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-remoting-testsuite-1.5?log=log20060320083115
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-remoting-testsuite-1.4?log=log20060320080353
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-cache-testsuite?log=log20060320072647
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/
Ryan,
When you are ready with jbossretro, pls create a jira task for me to
produce a snapshot that uses jbossretro. The jira task should conatin
instructions on howto run the build using jbossretro.
Cheers
-thomas
xxx
Thomas Diesler
Web Service Lead
JBoss Inc.
xxx
FYI, svn is much better about this. It does not distinguish between txt
and binary (i.e. it does not rewrite CR/LF) and uses a binary diff
algorithm
http://svnbook.red-bean.com/nightly/en/svn.forcvs.binary-and-trans.html
xxx
Thomas Diesler
Web Service Lead
JBoss Inc.
47 matches
Mail list logo
