On 2020-04-14 18:59, Andrea Aime wrote:
I agree... it has been like that for years, don't know of a good
solution... besides maybe
getting rid of all our custom maven plugins (not easy I'm afraid)?
Seems to be related to that, but not 100% sure.
The plugins could be moved to a separate source repo and release from
there and published to the osgeo maven repo; of the 3 only xmlcodegen
has dependencies on other geotools code, but that can probably be
resolved using dependency definitions as part of the plugin
configuration in the geotools project.
that way they don't have to be built during geotools builds because
maven can download from the defined pluginRepository.
jarcollector can probably be replaced with the maven assembly plugin,
though that would probably require a bit of fiddling getting it to work.
Mark
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
