Bug 220792

Comment 1 Martin Oberhuber 2008-02-28 13:06:30 EST

PS the background of this is that I'm maintaining several Eclipse installations, and distributing the archive to the various locations is easier than running the update manager on each site.

Comment 2 Markus Knauer 2008-02-28 13:10:05 EST

The PDE build output is a zip archive that we are extracting to the update site. That means it is a trivial step to make the zip archive available for download. I can do that in the next few days.

Comment 3 Martin Oberhuber 2008-02-28 13:30:34 EST

What you get from PDE Build for free is an "archived update site". Which is kind of OK (CDT only ships that kind of ZIP for downloads as well), but not really nice since it cannot be extracted into an Eclipse installation right away because it contains JAR'd features whereas Eclipse requires expanded features.

Our build process, (and others too, I believe), uses this for creating downloadable bits:

<target name="assemble.org.eclipse.tm.terminal.sdk">
	<property name="archiveName" value="TM-terminal-${buildId}.zip"/>
	<ant antfile="${assembleScriptName}" dir="${buildDirectory}"/>
	<antcall target="unpackUpdateJarsForPackaging" />
</target>

<target name="unpackUpdateJarsForPackaging" depends="myInit">
	<property name="tmpsite" value="${buildDirectory}/tmpsite" />
	<mkdir dir="${tmpsite}/new/eclipse/features" />
	<mkdir dir="${tmpsite}/new/eclipse/plugins" />
	<exec executable="unzip" dir="${buildDirectory}/${buildLabel}">
		<arg line="-q ${archiveName} -d ${tmpsite}" />
	</exec>
	<copy todir="${buildUpdateSitePath}">
	    <fileset dir="${tmpsite}/eclipse"/>
	</copy>

	<unpackUpdateJars site="${tmpsite}/eclipse" output="${tmpsite}/new/eclipse"/>
	<antcall target="packageLicenseFiles"/>
	<zip destfile="${buildDirectory}/${buildLabel}/${archiveName}"
		basedir="${tmpsite}/new"
  	/>
	<delete dir="${tmpsite}"/>
</target>

Comment 4 Martin Oberhuber 2017-04-20 15:19:09 EDT

I'll mark this WONTFIX as the UDC is deprecated by now:
https://www.eclipse.org/epp/usagedata/