Andrea Aime wrote: > I can see two paths: > - move back the eclipse output trick in a profile
I think this is the cleanest approach for now. How about -Peclipse-bin? I would be equally happy with leaving bin as the default and having a profile to turn it off (-Peclipse-shared). > - have the tests that need to register factories avoid using META-INF I am reluctant to modify the GeoTools codebase to meet the requirements of an IDE. This is an Eclipse problem, or more precisely, a maven-eclipse-plugin problem. I think a better fix would be to request a testOutputDirectory option for maven-eclipse-plugin, or an option to make it autogenerate target/classes-eclipse and target/test-classes-eclipse if some option is turned on (just change the output attributes in the classpathentry). This would fix the underlying problem without hacking GeoTools. Kind regards, -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
