Hi,
I am currently working on the testing builds, with two goals:
- bring them up to the agreed standards of the product builds, and
- allow them to run without recompiling the EclipseLink product jar(s).
During this effort, it has become apparent, that with a little more
work things could be made much easier for testing - both for our team,
and for users of EclipseLink. One of the things that would make
testing easier is to separate tests from the testing infrastructure.
This would allow the infrastructure to be built once and depended upon
by the tests, rather than having the test projects rely on a spaghetti
plate of inter-dependencies.
The change for development should simply mean another project in
eclipse that needs to be added once before tests will compile.
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=294732 to
track discussion about this issue. Please comment. I want to find out
if there is any pressing reason or strong opinions not to do this.
Thanks.
-Eric
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev