Whew, that's a mouthful.
So I found a bug/issue with maven 2.0.9 today.
I have the following pom structure:
geoserver/web/pom.xml -> triggers profile to include
gt-arcsde/datastore/pom.xml
in gt-arcsde/datastore/pom.xml a profile is activated to include an
extra jar
in the 'include that extra jar' the version string uses a property (
${sde.version} ) that was used to activate the profile, this property is
NOT properly expanded (and is actually ignored, reverting to the
default) in maven 2.0.9, but this structure works just fine in 2.0.8 or
lower.
Just a heads up that there are some weirdnesses in maven 2.0.9 in the
border cases. For now I've hard-coded the version of the pulled-in jar
in the profile (which makes sense anyway) but otherwise I'd have to
build with 2.0.8 or lower.
--saul
-------------------------------------------------------------------------
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
