The dependency on mdjts is a mistake. (I only see it in
UnionPerfTester). I'll remove this from CVS.
In any case, the test code is not included in the JTS jar, and the JTS
API codebase doesn't use JUMP (as far as I'm aware - if it does that's
an error). So I'm not sure how why you see a problem with a cyclic
dependency?
There isn't really a concept of "project" in the JTS CVS - all there is
in there is the src tree. If you're building from source, can't you
just remove those packages from *your* project?
Paul Austin wrote:
Martin,
I was wondering if you would consider moving the test classes in the
JTS project which depend on the mdjts. or com.vividsolutions.jump
packages to another project than the main JTS project. This will allow
for the main classes to be compiled without these dependencies. The
reasoning behind the com.vividsolutions.jump one is that the way it is
setup now you'd have a cyclic dependency between the JTS and JUMP
projects?
Cheers,
Paul
_______________________________________________
jts-devel mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jts-devel
--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022
_______________________________________________
jts-devel mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jts-devel
