So after some heroics (thanks Refractions, Dave and everyone) we are
finally back in the game.
We found that the number of dependencies in the "parent" pom actually
masks the real needs of a module like referencing.
According to the current sturcture, referencing needs batik for example.
I understand that it is nice to have a single place to go to update
version numbers, is there anything else we can do?
We are going to try to remove all dependencies from the parent pom, and
then count on transitive dependencies to carry things forward.
So the fact that referencing uses JTS would mean that API would not need
to say so explicitly.
The goal here is to have the GeoServer Data module that can depend on
main + data plugins and not get a dependency on batik.
The fact that the GeoServer WMS module depends on rendering will cause
batik to be included there.
Hope this make sense, and also the push for maven 2.
Jody
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
