I experimented a lot with the SDK generation and usage, as well as the target environments. There are two ways the SDK can be used: 1) According to the current SDK Quickstart, have a zip file, unzip it somewhere and set it as a "Directory" source in the target environment. In that way it's necessary to have all the features unpacked beforehand and some plugins too (those with "Eclipse-BundleShape: dir" in their manifest)
2) Use an SDK jar/zip file, like the one generated by tycho inside the udig_sdk-feature/target and set it as a "Software site" source in the target environment. You'd need to specify the SDK file as an archive update site, select the uDig SDK group and uncheck the "include required software". In that way no features or plugins needs to be unpacked beforehand. When Eclipse loads the target environment, it copies the features/plugins in the workspace and it automatically unpacks the ones that need unpacking. Note that in both ways the #1948 bug exists, as the net.refractions.udig.libs.source plugin is not generated according to the docs. The reassembling of that plugin (part of my sdk.sh patch) is needed. It'd be nicer if this can be done during the tycho building with some maven plugin. Currently my sdk.sh patch prepares the SDK for use in the first way. If you wish I can prepare another version that does not unpack the features/plugins and only reassembles the libs.source. The delta pack download can be avoided. There is no Update site for delta-packs; instead you can add in the target environment the Eclipse Project update site: http://download.eclipse.org/eclipse/updates/3.7 and choose the Eclipse platform feature version that is suitable (3.7.2 for current uDig SDK) Let me describe my setup a bit: I use Juno as my main IDE and in my uDig-based (and Indigo-based) app I use some other stuff like EMF Validation, Nebula widgets, Equinox transforms, etc. I wanted to avoid having to download various plugins and write instructions for the other devs on how to setup the target environment. I ended up with a .target file which includes everything I need, without having to manually download anything in particular (well except the SDK). Everything is added to the target env as a "Software site", an Eclipse update site. So some other dev, adds the target file into the workspace, opens it in the target file editor, selects the link "Set up as Target platform" and everything is loaded behind the scenes. Here are two snippets of my target file: For the Delta pack substitution: <location includeAllPlatforms="true" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> <unit id="org.eclipse.platform.feature.group" version="3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q"/> <repository location="http://download.eclipse.org/eclipse/updates/3.7"/> </location> For the uDig SDK (custom made 1.3.2 version): <location includeAllPlatforms="true" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> <unit id="net.refractions.udig_printing-feature.feature.group" version="1.3.2.201209262107"/> <unit id="org.eclipse.rcp.source.feature.group" version="3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272"/> <unit id="org.eclipse.platform.source.feature.group" version="3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q"/> <unit id="eu.udig.teradata-feature.feature.group" version="1.3.0.201209262107"/> <unit id="net.refractions.udig_application-feature.source.feature.group" version="1.3.2.201209262107"/> <unit id="org.eclipse.pde.source.feature.group" version="3.7.2.v20120120-1420-7b7rFUOFEx2Xnqafnpz0E--0"/> <unit id="net.refractions.udig_tutorials-feature.feature.group" version="1.3.2.201209262107"/> <unit id="net.refractions.udig_platform-feature.feature.group" version="1.3.2.201209262107"/> <unit id="net.refractions.udig_platform-feature.source.feature.group" version="1.3.2.201209262107"/> <unit id="net.refractions.udig_tutorials-feature.source.feature.group" version="1.3.2.201209262107"/> <unit id="org.eclipse.help.source.feature.group" version="1.3.0.v20110530-0844-7i7uFFmFFl8nvqbDpEqTvx"/> <unit id="net.refractions.udig_application-feature.feature.group" version="1.3.2.201209262107"/> <unit id="net.refractions.udig_printing-feature.source.feature.group" version="1.3.2.201209262107"/> <unit id="org.eclipse.emf.source.feature.group" version="2.7.2.v20120130-0943"/> <unit id="org.eclipse.gef.source.feature.group" version="3.7.2.v20110927-2020-777D381B4Bz0755B465D34242"/> <unit id="org.eclipse.xsd.source.feature.group" version="2.7.1.v20120130-0943"/> <unit id="net.refractions.udig_base-feature.feature.group" version="1.3.2.201209262107"/> <repository location="jar:file:/mnt/work/udig/sdk/udig-1.3.2-sdk-updatesite-pana.jar!/"/> </location> -Panagiotis On Wed, Oct 3, 2012 at 3:58 AM, Jody Garnett <jody.garn...@gmail.com> wrote: > Thanks I will try those patches now. > > I am a bit confused by your email? It sounds like I can either: > a) accept your sdk.sh script to unpack things; or > b) change the SDK Quickstart and ask people to point tot he sdk.zip file? > > I like the idea of referring to the zip file, it is less confusing then > the instructions about un zipping into a specific directory structure. > > Do you know we we can include the RCP Delta pack using the same facility? > Currently that is the hardest part of the instructions ... > > Jody > > _______________________________________________ > 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
