Hello Landon
Maven is difficult and unfortunatly not bug free. But I'm not aware of much
alternative... The goal was to allow developper to just invoke "mvn install"
from the root and get everything built, including dependencies.
Part of current difficulties is that our Maven configuration got lot of patches
and lot of profiles over time. We have ordinary tests and "online tests",
different set of profiles for building different set of modules (unsupported,
etc.). This has lead us to the point where, as you point on, no one understand
completly our own Maven configuration. Generating javadoc for example became
black magic.
I do think that the GeoTools project would benefit from being splitted into
different projects, where "GeoTools" would become an umbrella for synchronizing
those projects. Utilities/metadata/referencing modules could be managed in a
standalone project (well, this is more or less my idea with "geotiy"...), other
modules could be managed as an other project having the first one in their
dependencies, etc. Each one may have their own build system. Geotidy for
example
has a much simplified Maven configuration compared to the GeoTools one, which
allow us to get the JAR deployed, web site and javadoc generated, "everything
in
one big JAR file" bundles created nightly. I have not be able to get the same
in
geotool. This may be possible, but would require hard work.
However if your project were using an other build system, and if your project
is
popular, there is a hight probability that users would ask for a maven build in
addition to your build. This is in order to get your JAR deployed on some Maven
repository. And also because some will want to learn only one build system
(Maven) instead than a different build system for each module.
So in summary this is true that the GeoTools Maven build is complex and need
lot
of rework. And some kind of flexibility may be gained if GeoTools become an
umbrella for interrelated projects. But I guess that we would ask that every
project get at least their JAR files deployed on a Maven repository, even if
they use internally an other build system.
Martin
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
