Hi,
I just pulled down the gs-web-app war artifact for the 2.5.2 release and
noticed some commingling of 2.5.2 and 2.6-beta geoserver along with 11.2
and 12-beta geotools jars (and transient dependencies) in WEB-INF/lib. It
appears that this artifact was packaged and deployed without running the
maven "clean" first. I tried to dig into this and looked at the release
job logs on http://ares.boundlessgeo.com/jenkins/
It looks as if jobs were run in this order:
1) 2.5.2 was built with "geoserver-release" job in a directory (mvn clean
install)
2) 2.6-beta was built with "geoserver-release" job in same directory (mvn
clean install)
3) 2.5.2 was published with "geoserver-release-publish" job in same
directory (mvn deploy)
This last job is problematic as "mvn deploy" also runs through the
"package" phase and without a "clean" the build target directories can have
files from prior builds (2.6-beta in this case)
I've only looked at the 2.5.2 gs-web-app war artifact and it's tainted with
2.6-beta jars. There may be other published 2.5.2 release jar artifacts
with issues.
--
* Tom Kunicki* | Software Engineer
*w:* 608 695 4251 *e:* [email protected]
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
