|
| Re: Problems building an update site with bucminster [message #378402 is a reply to message #378400] |
Thu, 03 July 2008 13:30   |
|
Rich Scott wrote:
> I have been trying to get started with Buckminster by building an update
> site. I have followed the example at
> http://wiki.eclipse.org/Buckminster/Examples/Building_an_Upd ate_Site.
> and created an update site project with cspec. Invoking the build.site
> action runs successfully, but the resulting output is not what I was
> expecting for an update site. I was expecting the site to contain the
> site.xml, index.html along with populated plugins and features
> directories. Instead the site contains a file for each plugin with name
> like <plugin_name>_<version>-osgi.bundle.
You are looking at the individual builds of each component. There will
be one just like it named <your update site>_<version>-buckminster. In
that folder, you will find folder name site. This folder contains a zip
file which in turn contains the complete update site.
Regards,
Thomas Hallgren
|
|
|
|
| Re: Problems building an update site with bucminster [message #378406 is a reply to message #378404] |
Thu, 03 July 2008 13:57 |
|
Hi Rich,
Buckminster doesn't have anything built in for this (yet). For our own
purposes, I created an ant target that looks like this:
<target name="p2ize.site">
<delete dir="${output.folder}" />
<mkdir dir="${output.folder}" />
<unzip src="${input.file}" dest="${output.folder}/unzipped" />
<delete file="${output.folder}/unzipped/pack.properties" />
<pathconvert property="siteURL" dirsep="/">
<path location="${output.folder}/unzipped/"/>
</pathconvert>
<java jar="${launcher.jar}" fork="true" failonerror="true">
<arg value="-application" />
<arg
value="org.eclipse.equinox.p2.metadata.generator.EclipseGenerator " />
<arg value="-updatesite" />
<arg file="${output.folder}/unzipped" />
<arg value="-site"/>
<arg value="file:${siteURL}/site.xml" />
<arg value="-metadataRepository"/>
<arg value="file:${siteURL}" />
<arg value="-metadataRepositoryName"/>
<arg value="Buckminster Update Site" />
<arg value="-artifactRepository"/>
<arg value="file:${siteURL}" />
<arg value="-artifactRepositoryName"/>
<arg value="Buckminster Artifacts" />
<arg value="-compress"/>
<arg value="-reusePack200Files" />
</java>
<zip basedir="${output.folder}/unzipped"
destfile="${output.folder}/${subject.file}" />
<delete dir="${output.folder}/unzipped" />
</target>
(you will find it in the make/eclipse-signing.ant file in the source of
the org.eclipse.buckminster component)
Regards,
Thomas Hallgren
Rich Scott wrote:
> Thomas Hallgren wrote:
>
>> Rich Scott wrote:
>>> I have been trying to get started with Buckminster by building an
>>> update site. I have followed the example at
>>> http://wiki.eclipse.org/Buckminster/Examples/Building_an_Upd ate_Site.
>>> and created an update site project with cspec. Invoking the
>>> build.site action runs successfully, but the resulting output is not
>>> what I was expecting for an update site. I was expecting the site to
>>> contain the site.xml, index.html along with populated plugins and
>>> features directories. Instead the site contains a file for each
>>> plugin with name like <plugin_name>_<version>-osgi.bundle.
>
>> You are looking at the individual builds of each component. There will
>> be one just like it named <your update site>_<version>-buckminster. In
>> that folder, you will find folder name site. This folder contains a
>> zip file which in turn contains the complete update site.
>
>> Regards,
>> Thomas Hallgren
> Thomas,
>
> Thanks for the insight. That was easy.
> I need to have a p2 enabled update site. Can I configure Buckminster to
> use the PDE build support for p2 by adding the required *p2* properties
> somewhere, or do I need to incorporate p2 agent into the build stream?
>
> An suggestions on the best direction or pointers to reference info would
> be appreciated.
>
> Thanks
> Rich
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04182 seconds
] 
Search
Help
Register
Login
Home
