um it is easy; we currently do it? We grab the project.version from our parent
pom.xml.
In the dawn of time (like GeoTools 2.0) we experimented with allowing module to
each have their own version number; the resulting confusion as people tried to
sort out what jars would work together was like a slow moving train wreck with
a cattle car of bulls hitting a china shop and moving on to glassworks followed
by a natural gas refinery.
It is just that we never updated the developers guide to match what we actually
do.
--
Jody Garnett
On Thursday, 7 April 2011 at 8:44 AM, Michael Bedward wrote:
> On 7 April 2011 01:33, Jody Garnett <[email protected]> wrote:
> > In particular we do not allow modules to each have their own version number.
>
> That's really hard to do in a maven-based modular project. I recently
> investigated it for jai-tools and there was no off-the-shelf solution,
> only one or two experimental plugins.
>
> Michael
>
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
