Hi,
ok, I'm uploading artifacts to sourceforge and 2.3.x is open for
business again.
Yet, releasing took me some 8 hours, and I want to share some of
the issues I've had, a few could have been avoided.
1) the build did not work with interactive tests and extensive tests.
The former cannot be checked with build servers, but the latter do.
I had to issue two fixed, one in the coverage module, trivial, and
another that sucked away quite a bit of time because I had to track
it down just to discover the EPSG database is broken for a single
coordinate transformation.
2) checking out a fresh copy from the tag took forever (more than 30
minutes). Hmm... is the refractions svn server using gzip
compression? Anyways, today my connection towards Europe works fine,
but crossing the ocean does not work at all (slow, unreliable)
3) the rename using msys find and sed did not work, and using Ant simply
OOM'd after a few minutes (great). In end I used a GUI tool that did
the job "Simple Search and Replace".
4) deploy to lists.refractions.net required around 4 hours. I made
three failing attempts from the root of geotools, but after some time
the server just kicked me out "socket connection reset". Last
successfull attempt saw me do deploy in maven, main, plugin, ext and
demo separately, and worked (taking 1 hour 20 minutes thought).
Most of the time is not spent uploading (upload speed was good,
30Kb/s), but in redirections:
INFO: Redirect requested but followRedirects is disabled
12-apr-2007 12.03.38 org.apache.commons.httpclient.HttpMethodBase
processRedirectResponse
Codehaus seems to be more reliable deploy wise. Oh, I also noticed
that wagon-ftp seems now to work, and ftp should be a much better
way to upload stuff.
5) During the last attempt, I noticed generating source jar for
demo-introduction was stuck for minutes, sucking 10MB/s from my disk,
and with a strange message, too:
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar:
C:\progetti\geotools\2.3.1\demo\introduction\target\gt2-demo-introduction-2.3.1-sources.jar
This happened only doing a mvn deploy from the demo directory.
Trying the same from /introduction resulted in test failures, which
are obvious, since the module is trying to make shapefile datastore
load a shape from classpath without copying it out of the jar.
Works fine in Eclipse, where the file can be accessed direclty,
fails in maven testing, but strangely only doing a mvn install
in the /introdution directory.
Well, in the end, I simply removed the introduction module from the
release
6) Testing the source release with an empty repository took 1.5 hours.
Yeah, you read properly, 1.5 hours. Sigh, damn ibiblio.
Ok, I'm almost done uploading the release artifacts to sourceforge
(another 40 minutes at 20kb/s).
I'd say, the release notes should state that you need either to live in
North America, or have a professional internet connection to do
a release, with my private user one it's really a pain (thought I can
download 650MB in 20 minutes if I'm downloading from a fast european
site...)
Cheers
Andrea
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
