[
http://jira.jboss.com/jira/browse/JBAS-1598?page=comments#action_12316851 ]
Ivelin Ivanov commented on JBAS-1598:
-------------------------------------
________________________________________
From: Scott M Stark
Sent: Monday, April 11, 2005 1:00 PM
To: Clebert Suconic; '[EMAIL PROTECTED]'
Subject: RE: Create a compatibility matrix which tracks JBoss client vs. server
class versions
Serialization should be mostly covered by the SerialVersionUIDUnitTestCase in
the bundled testsuite. There needs to be basic testing of all j2ee interfaces
by running a subset of the existing testuite modules against the current jboss
server. This is not hard.
1. For each release of jboss there is a build of the release source.
2. The current jboss server branch is obtained and built.
3. The current jboss server branch binary is run as with the all configuration.
4. For each release of jboss:
a. Run a subset of the testsuite unit tests from within the release build
so that the release build binaries are used.
5. Merge the testsuite runs into a cross version compatibility matrix. The
toplevel view is a simple pass/fail matrix which indicates whether all of the
tests run using the x.y.z binaries passed.
________________________________________
From: Clebert Suconic
Sent: Monday, April 11, 2005 10:52 AM
To: Scott M Stark; '[EMAIL PROTECTED]'
Subject: RE: Create a compatibility matrix which tracks JBoss client vs. server
class versions
We will need to test Serialization across versions or functionalities across
version as well?
I'm afraid about the answer you would have, as if we have to test
functionality, the amount of work will be huge. What if the Serialization
works, but it the interceptor on 4.0.1 puts something different on the
Marshalling that the stubs are not prepared to receive. (Just wondering some
breaking in the functionality)
But If it's serialization only, we can do it fast.
Clebert
________________________________________
From: Scott M Stark
Sent: Monday, April 11, 2005 12:42 PM
To: Clebert Suconic; '[EMAIL PROTECTED]'
Subject: RE: Create a compatibility matrix which tracks JBoss client vs. server
class versions
No, that is not enough. We need an independent test matrix that is run as part
of the nightly qa process that runs the testsuite using the x.y.z release jars
against the current 4.0 branch to validate actual functional behavior.
Serialization version ids are only one small part of version interop.
Addition/removal of classes, and changes in implementation are the other big
factors that break interop. The serialization version uid test is the only one
that should be part of the normal development testsuite. The cross version
matrix needs to be external and not part of the testuite cvs module so as not
to bloat the download.
________________________________________
From: Clebert Suconic
Sent: Monday, April 11, 2005 9:49 AM
To: Scott M Stark; '[EMAIL PROTECTED]'
Subject: RE: Create a compatibility matrix which tracks JBoss client vs. server
class versions
I can extend what you did into http://jira.jboss.com/jira/browse/JBAS-1584
Do you think that if I compare SerialUID from previous versions against actual
version would be enough to keep this compatibility matrix, or should we be
doing something beyond that?
Also... I created a simple testcase that verifies if classes are defining UIDs.
As cruisecontrol is broken for 4.0 now, I think people haven't look at the
results. I think we still have classes not defining SerialUUID. My
understanding is that this matrix is dependent of clearing SerialUUIDs first.
Is that right?
Clebert
________________________________________
From: Scott M Stark
Sent: Monday, April 11, 2005 12:08 AM
To: [EMAIL PROTECTED]
Subject: Create a compatibility matrix which tracks JBoss client vs. server
class versions
What is the status of this issue?
http://jira.jboss.com/jira/browse/JBAS-1598
> Create a compatibility matrix which tracks JBoss client vs. server class
> versions
> ----------------------------------------------------------------------------------
>
> Key: JBAS-1598
> URL: http://jira.jboss.com/jira/browse/JBAS-1598
> Project: JBoss Application Server
> Type: Sub-task
> Reporter: Ivelin Ivanov
> Assignee: Clebert Suconic
>
>
> The matrix should list JBoss client jars, the version of their JBoss distro
> and the respective JBoss versions that the clients are compatible with. For
> example (not verified)
> | JBoss AS Client Jars | Compatible with JBoss AS versions |
> | ---------------------|-----------------------------------|
> | 4.0.2 | 4.0.2, 4.0.1 |
> | 3.2.7 | 3.2.6, 3.2.5 |
> ------------------------------------------------------------
> Ideally the matrix should be maintained and updated as part of the build
> process using the automated tests from JBAS-1584.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
