I was so deeply involved creating the release that I didn't realized something could have changed for the sdk procedure.
Let me explain:
for uDig development itself we are going through the following steps:
- download an Eclipse IDE (preferred with EMF Modeling tools)
- download an JRE (from Refractions with JAI/Image IO and optionally with gdal natives - not available for mac osc)
- clone the repository
- import target project from targets folder
- open the target file (at the time of writing ./targets/indigo/udig-indigo-target.target)
- set as target platfrom
- import required plugins/features from git clone
- start developing
What do you think about doing something similar for the udig-sdk than suggesting every body else to do it in an other way
And here IMHO the procedure should look like:
- download preferred Eclipse IDE (my one is 4.3 btw.)
- download JRE (w/o GDAL and JAI/Image IO)
- open a new eclipse workspace
- setting up a new target environment:
- add udig-sdk update site (suggestion : http://udig.refractions.net/files/update/latest/udig-sdk)
- describing a way how to add 3rd-party dependencies:
- eclipse (emf, gef, ...)
- eclipse babel (i18n - if necessary)
- eclipse babel (logging, testing, etc.)
-
refractions JAI/Image IO update site
--> we would end up in a file that content would look like our current target-definition file mentioned above (except the udig-sdk url), therefor I would like suggest
- to download the target definition file (we could attach it to udig devel docs as a file referenced in the SDK Quickstart guide)
- create a simple workspace project and add this target file
- modify it and add the prefered udig-sdk update site (see above)
- set this as new target platform
- if the potential developer need sources for the referenced update-sites it would be pretty easy to do so: set the property includeSource like this:
includeSource="true"