Interesting. 

I depend on the "ire" bundles I download to contain the gdal data directories; 
the scripts just unzip everything into the same spot. So perhaps it got left 
out last time the JREs were made (perhaps for uDig 1.2.2 onward?)

I have done my best to document my setup for release in the wiki; from there I 
just run the shell scripts.

Let me check what I have in deploy/jre

lrwxr-xr-x   1 jody  staff    46 29 Jun  2011 jre1.6.0.linux.x86_64.zip -> 
/Users/jody/java/jre/jre1.6.0.linux.x86_64.zip
lrwxr-xr-x   1 jody  staff    39 29 Jun  2011 jre1.6.0.win64.zip -> 
/Users/jody/java/jre/jre1.6.0.win64.zip
lrwxr-xr-x   1 jody  staff    54 29 Jun  2011 jre1.6.0_25.lin32_gdal_ecw.tar.gz 
-> /Users/jody/java/jre/jre1.6.0_25.lin32_gdal_ecw.tar.gz
lrwxr-xr-x   1 jody  staff    54 29 Jun  2011 jre1.6.0_25.lin64_gdal_ecw.tar.gz 
-> /Users/jody/java/jre/jre1.6.0_25.lin64_gdal_ecw.tar.gz
lrwxr-xr-x   1 jody  staff    51 29 Jun  2011 jre1.6.0_25.win32_gdal_ecw.zip -> 
/Users/jody/java/jre/jre1.6.0_25.win32_gdal_ecw.zip
-rwxr-xr-x   1 jody  staff  4732 23 Feb  2011 linux_jre_build.sh


Okay that was a side step let me try my java/jre folder:

-rw-r--r--@  1 jody  staff  30707770 29 Jun  2011 jre1.6.0.linux.x86_64.zip
-rw-r--r--@  1 jody  staff  36811865 29 Jun  2011 jre1.6.0.win64.zip
-rw-r--r--@  1 jody  staff  46841124 29 Jun  2011 
jre1.6.0_25.lin32_gdal_ecw.tar.gz
-rw-r--r--@  1 jody  staff  53584630 29 Jun  2011 
jre1.6.0_25.lin64_gdal_ecw.tar.gz
-rw-r--r--@  1 jody  staff  48623995 29 Jun  2011 jre1.6.0_25.win32_gdal_ecw.zip


Those should be the latest as downloaded from our website; I think moovida put 
them together for me?

Checking my deploy/build directory (where things are staged for release).

linux32/udig/gdal_data/ exists!
linux64/udig/gdal_data/ exists!
win32/udig/gdal_data/ exists!
win64/udig/ ... does not exist :(

So one of them is bad... I will try and redownload? Let me check ...

http://udig.refractions.net/files/downloads/jre/

Nope; we just don't have a win64 build of gdal available :(

Perhaps the best way to volunteer would be to follow the instructions with a 
couple people on IRC to lend a hand and provide testing? 

-- 
Jody Garnett


On Wednesday, 11 January 2012 at 10:02 PM, Frank Gasdorf wrote:

> Hello Developers,
> 
> I reviewed some udig classes (e.g. 
> net.refractions.udig.catalog.imageio.Activator) and expected to find a 
> gdal_data folder in the udig root folder of installations. In addition I had 
> a look into the release scripts to find out whats going on during packaging 
> udig releases before upload. I could not find any gdal_data copy process. 
> After that I checked out the releases since 1.2.2 and that's confusing me:  
> windows 1.2.2 (32 bit release) contains the gdal_data directory
> BUT 
> windows 1.2.2 (34 bit release) doesn't
> 
> I'm missing the folder in the 1.3.x series as well. I guess some steps were 
> missing during the release process 
> (https://github.com/uDig/udig-platform/blob/master/deploy/installer/readme.txt)
>  : 
> 
> "1. Create a fresh archive release of uDig; copy in the jre and gdal_data as 
> a a subfolder to the
>    udig directory (as per the win32.sh (http://win32.sh) shell script)"
> 
> properly Jody can clarify a bit. I'll try to step through the release 
> process, properly we can make it easier by invoking pure maven 
> (eclipse-application) and switch over to eclipse-repository packaging type 
> and manipulate after  packaging the resulting zip (platform dependent start 
> scripts and copying required folders and files into the zip (using 
> maven-ant-tasks). 
> 
> Suggestions? Feedback? How would like to volunteer to make the release 
> process "stable"?
> 
> Thanks, Frank 
> 
> 
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel
> 
> 


_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel

Reply via email to