well, good to know I wasnt going crazy alone... it sounds to me we need a maven guru to work up a solution then we can delegate the application of the solution to the module maintainers.
a thought, for poking fun at: If we started with the core of GeoTools, the GeoTools developers would start getting the benefit of being able to work more efficiently in their modules, or the problems of the day, and hopefully propagate the best practice so the next dependency starts to get the benefit. Ideally if the exploitation of the solution required you to set up your project the same way then the propagation should happen. Also I notice some utility plugins seem to be wanted fresh every time eg org.codehaus.mojo:jalopy-maven-plugin:1.0-SNAPSHOT do we really really need to use SNAPSHOTs for these common utilities? Rob On Tue, Nov 25, 2008 at 9:41 AM, Michael Bedward <[EMAIL PROTECTED]> wrote: > 2008/11/25 Andrea Aime <[EMAIL PROTECTED]>: >> Soo... I don't know. I can't think of a good way to stamp a GT2 >> module so that it's possible to tell when it was modified, and >> when it's not. >> > > As well as the maven reactor plugin, which may or may not help, there > is this one which may address the timestamp issue (?) > > http://mojo.codehaus.org/buildnumber-maven-plugin/ > > Michael > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
