From: <ron...@ho...> - 2012-01-27 22:54:58
|
Hi, Thanks for chiming in, Martin. > > When I tested Ron's file, I tested it alongside a new build of our own > from our Jenkins server > <http://plum.hcmc.uvic.ca:8080/job/eXist1.5_WAR_OracleJDK1.6/> (at the > time it was rev 15735). In our build, the JNLP worked absolutely fine. > So I suspect the problem may be something to do with the build > process, or the fact that Ron's building on Windows. Can anyone else > building 1.5 on Windows test this out? > Now things are starting to get really weird. I've spent my evening repeating the build steps on our Ubuntu Linux web server, using Martin's build script verbatim. Guess what: the generated .war file behaves identical when it comes to serving exist.jnlp (the file is empty). Both on the Ubuntu Linux Tomcat and my Windows 7 one. It made me desperate enough to repeat the build exercise on an older Windows Vista computer: same result. I've uploaded the Ubuntu-generated war file at <http://ctb.kantl.be/temp/exist-1.5.0dev-rev15744.war>. How can a completely fresh eXist checkout with exactly the same build script produce different builds, that -on my side- fail to work on no matter what configuration I build/use them? I'm getting really curious if other (Windows?) users at all are experiencing the same behaviour. Kind regards, Ron |