[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-dev] Tests that involve multiple componenets
|
The way I envisioned this working is that the JAXB test suite would only be
dependent on the JAXB/MOXy project (which would depend on a Core/Foundation
project). Then there would be a separate test project for combining the
different technologies for end-to-end scenarios (i.e. reading data using JPA
and then serializing the POJOs to XML using JAXB, or exposing JPA data as
SDO).
-Blaise
----- Original Message -----
From: "Gordon Yorke" <gordon.yorke@xxxxxxxxxx>
To: "Dev mailing list for Eclipse Persistence Services"
<eclipselink-dev@xxxxxxxxxxx>
Sent: Thursday, September 06, 2007 1:37 PM
Subject: RE: [eclipselink-dev] Tests that involve multiple componenets
An "end to end testing component" just displaces the problem. Users wishing
to run the full suite of JAXB tests would still need to build all other
components in order to have the "end to end testing component" build.
Perhaps creating subdirectories within the testing components with the
different groups of tests organised into a directory would be a better
solution. Users could easily eliminate the test groups that they were not
interested by only including the tests that they were interested in.
Testing suites could be better organised by test group.
--Gordon
-----Original Message-----
From: eclipselink-dev-bounces@xxxxxxxxxxx
[mailto:eclipselink-dev-bounces@xxxxxxxxxxx]On Behalf Of Tom Ware
Sent: Thursday, September 06, 2007 10:13 AM
To: Dev mailing list for Eclipse Persistence Services
Subject: [eclipselink-dev] Tests that involve multiple componenets
Hey Folks,
At the moment the EclipseLink repository is configured with a project
for each component and no circular compile dependancies between those
projects.
We are starting to be ready to check-in some tests that make use of
multiple components. (e.g. A JAXB/JPA test)
It does not really make sense to check that kind of a test in to
either the JAXB or the JPA testing projects since neither project should
depend on the other and the JPA tests should not depend on the JAXB core
and vice versa.
I am looking for suggestions about how to set this up.
The current best suggestion I have is to set up an End-toEnd testing
component that depends on all other projects that can include any
end-to-end testing.
What does everyone think?
-Tom
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
