I was just asked about this on IRC; so to follow up Martin's email... > In a little bit longuer term, I wonder if we should consider make the > GeoTools project to evoluate toward a structure like Jakarta - an > umbrella for sub-projects with coherent package names, policies and > the same parent pom.xml and JIRA tracker, but where the "sub-projects" > would live in their own OSGEO's SVN, have their "maven build" process > and releases. For other modules like XSD, running "mvn eclipse" would > mount only the JAR rather than the sources, which would solve Justin's > problem since jaxb-dummy do not appears in dependencies. I guess that > peoples could still mount the sources if they wish. It may also > provides a little bit more flexibility for providing many flavors of > referencing, like "with jaxb", "without jaxb", "all in one fat jar", > "trimmed version with only a few selected functionalities" (for those > who consider referencing too big), etc. It would be hard to trick the > build for providing all those flavors while keeping the same build > compile the whole GeoTools projects, while it may be slightly easier > if the build doesn't need to care about modules after "referencing". > It would also reduce the build time for those who don't work on > metadata and referencing. > > This is just an idea. Producing additional "GeoTools" products is a good idea; in terms of product development this idea would let us target specific user communities more effectively. I would like to revisit this idea after we have completed OSGeo graduation (I can only handle a couple large "community" tasks at a time).
Cheers, Jody ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
