Jody Garnett a écrit :
> Martin also suggested we could simplify - martin do you have specific
> ideas of complexity that can be stripped out of our maven configuration?
We could try to reduce the amount of profiles as much as we can. For example
the
"ordinary tests" vs "OnlineTest" setting could be removed. We can achieve the
goal we were aiming with "OnlineTest" by using the new JUnit 4 "assume" feature
instead ("run this test only if condition xyz is meet"). We could also rename
the directory name so they match exactly the module name - it would allow us to
get ride of <scm> and other setting repeated in every modules. If we were on a
distributed versionning system, the "supported" vs "unsupported" list of
modules
could be handled as two (or more) distincts clone of the GeoTools repository.
This is just some idea that popup from my mind right now. But we may not need
action right now. For example all the above are already applied in geotidy, so
if this project get linked to geotools later, those actions would be partially
done. In addition if the geotools project become an umbrella for sub-projects,
the whole geotools community would get faster build since the majority of
developpers don't need to recompile metadata and referencing at every build.
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
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
