If we do (2) the docs will need to wait, anyway. All the EJB3 examples
will clash with the new release.
Including the codegen in the tools;(
/max
Scott M Stark wrote:
HEM 3.1beta5 is not a valid release as it references a
ejb3-persistence.jar that does not exist in the
On Tue, 10 Jan 2006 10:34:59 +0100, Gavin King [EMAIL PROTECTED]
wrote:
Including the codegen in the tools;(
Shit. That's right. I will need to update that stuff.
Straightforward, I suppose.
probably, but needs to be very much aligned, since i'm want to da a bugfix
release so
if
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110045823Lbuild.1170
BUILD COMPLETE-build.1170Date of build:01/10/2006 04:58:23Time to build:10 minutes 21 secondsLast changed:01/10/2006 04:42:36Last log entry:Remove
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20060110060259Lbuild.667
BUILD COMPLETE-build.667Date of build:01/10/2006 06:02:59Time to build:8 minutes 52 secondsLast changed:01/10/2006 05:52:53Last log entry:Fix testsuite
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110073537
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
This is fixed. The cglib code that you introduced in jbossws has a
dependency on asm-1.5.3, wchich is not compatible with asm-3.0_beta used
by the retrotranslator. Other modules have similar dependency. I now
bundle an obfuscated version of asm-3.0_beta with the
retrotranslator-0.9.6jboss.jar
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110081757
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
I would prefer you to maintain a single jbossxb version in HEAD with
known binary drops in the repository that are then beeing used in 4.0.x.
Otherwise I have little confidence that we will get retrotranslated
versions of projects that depend on jbossxb (like JBossWS) working in
4.0.x
Currently,
So, after Scott said we can't have 'snapshot' you renamed snapshot to
RC1? I don't think this is what the problem was...
Thomas, I think, you are going to fast w/o decisions made on forums or
dev list. This way you may create more problems than solve.
You did start the discussion
Hi
folks,
I completed
thework arround using retrotranslator.
The good
news first
---
The new web
service stack can be used in 4.0.x without known limitations. This will give
cutomers ws-security, ws-addressing, ws-eventing, jsr-181 annotations, ejb3
endpoints, etc.
The snapshot version is a placeholder for itermediary versions. 1.0RC1
is the now verified version that passes all webservice tests in 4.0.x.
I'm happy with whatever solution you can provide that allows jbossws-1.0
to be used with the upcomming 4.0.4 release. This is necessary to
provide our
and the bad news is? :)
Congratulations, that's great!
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Thomas DieslerSent: mardi, 10. janvier 2006 14:57To:
Dev - JBossWS; Alexey Loubyansky; Scott M Stark; Jason T. Greene; Sacha
Labourey; Ivelin IvanovCc:
The compatibility tests need to run the signature tests
because there were some changes to the j2ee module classes that I doubt will
pass. If they do not, the webservice interface classes need to be factored out
to choose between the j2ee 1.4 and java ee 5 versions.
From: Thomas
The first question is can a fork of head be easily made compatible with
the apis that existed in the 4.0 branch before th merge. I'm looking at
some of the test changes now.
-Original Message-
From: Thomas Diesler
Sent: Tuesday, January 10, 2006 6:14 AM
To: Alexey Loubyansky
Cc:
Awesome
-Jason
From: Thomas Diesler
Sent: Tuesday, January 10, 2006
7:57 AM
To: Dev - JBossWS; Alexey Loubyansky; Scott M
Stark; Jason T. Greene; Sacha
Labourey; Ivelin Ivanov
Cc:
jboss-development@lists.sourceforge.net
Subject: JBossWS-1.0RC1 release
works in 4.0.x
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110131421
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
We also need a jdk5 compiled version under a different
version for inclusion in profiles like ejb3 that require jdk5, and for users
that run with jdk5.
http://jira.jboss.com/jira/browse/JBAS-2645
From: Thomas Diesler Sent: Tuesday,
January 10, 2006 5:57 AMTo: Dev - JBossWS;
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110144824
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060110145621Lbuild.1
BUILD COMPLETE-build.1Date of build:01/10/2006 14:56:21Time to build:1 minute 53 secondsLast changed:01/10/2006 02:03:07Last log entry:make it Local
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110153411
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110171308
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
Webservices is breaking the build in a 1.4
JDK:
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 10, 2006
4:20 PM
To: Anil Saldhana;
[EMAIL PROTECTED]; Dimitris Andreadis;
jboss-development@lists.sourceforge.net; QA; Rajesh Rajasekaran; Scott M Stark;
module-webservice14:BUILD FAILED/services/cruisecontrol/checkout/jboss-head/build/build.xml:631: The following error occurred while executing this line:/services/cruisecontrol/checkout/jboss-head/build/build-distr.xml:1432:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110173630
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
This can also been found in the repository
under jboss/jbossws-1.0RC1
We have:
jbossws14.sar
jbossws14-client.jar
for jdk-1.4
jbossws.sar
jbossws-client.sar
for jdk-1.5 respectivly
cheers
-thomas
From: Scott M Stark
Sent: 10 January 2006 20:49
To:
Yes, but that is not properly seperated as the way the
component-info.xml reads currently, all 4 jars are required if you import the
jboss/jbossws component of version 1.0RC1. Also, the jbossws.sar and
jbossws-client.sar should have no dependency on retrotranslator. These need to
be two
Bugs item #1402221, was opened at 2006-01-10 23:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=1402221group_id=22866
Please note that this message will contain a full copy of
How are we going to handle components that
have a 1.4 and 1.5 version?
Are we going to offer two downloads for JBoss AS?
A JDK 1.5 profile and a JDK 1.4 profile?
Or are we going to somehow detect the jdk
version and alter the classpath on startup?
Or are we going to have a new
The installer is the only current mechanism for obtaining
java ee 5 features. It offers non-standard profiles that require jdk5. These
cannot technically be bundled with the j2ee 1.4
distributions.
From: Jason T. Greene Sent:
Tuesday, January 10, 2006 3:45 PMTo: Scott M Stark;
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110195150
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110210546
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110213255
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
One incompatibility is the change of the SchemaBindingResolver method
from:
SchemaBinding resolve(String nsUri, String localName, String baseURI,
String schemaLocation)
to:
SchemaBinding resolve(String nsUri, String baseURI, String
schemaLocation)
I suppose this is a minor issue as this is
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060110224730
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060111012742
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060111015221
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060111022237
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
37 matches
Mail list logo
