Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Headless build an update site with multiple features
Headless build an update site with multiple features [message #42183] Fri, 23 January 2009 17:36 Go to next message
Eclipse UserFriend
Originally posted by: eclipse-news.rizzoweb.com

I've seen many examples, articles, blogs, etc. about using PDE headless
build and some of them even talk a little about building an update site
headlessly. But what I can't seem to find is any help in building an
update site that includes multiple features, which may or may not all
change at the same time.
We have a current update site build that is a hack-job customization of
PDE Build, but it was done under the assumption of a single feature. Now
that we are offering multiple features, what we have won't work without
major changes. Seeing as it is a hack anyway, I'm looking for more
guidance and a better approach.

Is there any material out there that covers this specific use case? Is
anyone interested in providing some direct help that I would then turn
into a public article or tutorial? My company is desperate to get this
working in a "clean" way and want to contribute something back to the
community if we can reach that goal.

Thanks in advance,
Eric
Re: Headless build an update site with multiple features [message #43032 is a reply to message #42183] Thu, 29 January 2009 19:36 Go to previous message
Miles Parker is currently offline Miles ParkerFriend
Messages: 1341
Registered: July 2009
Senior Member
Coincidently, I'm in the same quandry, Eric.

First, it seemed relativly simple to get the build working with
multiple features. Just take the off the shelf templates and in
allElements.xml replace:

<target name="allElementsDelegator">
<ant antfile="${genericTargets}" target="${target}">
<property name="type" value="${topLevelElementType}" />
<property name="id" value="${topLevelElementId}" />
</ant>
</target>

with:

<target name="allElementsDelegator">
<ant antfile="${genericTargets}" target="${target}">
<property name="type" value="feature" />
<property name="id" value="my.great.feature" />
</ant>
<ant antfile="${genericTargets}" target="${target}">
<property name="type" value="feature" />
<property name="id" value="another.great.feature" />
</ant>
...
</target>

All of my features and plugins then get built into an update site. But
I was confused because build.properties seems to want to specify one
and only one feature.

I thought that that might have been causing related issues, so instead
I'VE created an overall feature that simply includes all of the
features I want. (I gather from an earlier posting that I can make that
feature invisible by not including feature.xml in the build.properties.)

But now I'm stuck on a couple of other issues -- I'll put in anothe
post to avoid confusion..


On 2009-01-23 09:36:44 -0800, Eric Rizzo <eclipse-news@rizzoweb.com> said:

> I've seen many examples, articles, blogs, etc. about using PDE headless
> build and some of them even talk a little about building an update site
> headlessly. But what I can't seem to find is any help in building an
> update site that includes multiple features, which may or may not all
> change at the same time.
> We have a current update site build that is a hack-job customization of
> PDE Build, but it was done under the assumption of a single feature.
> Now that we are offering multiple features, what we have won't work
> without major changes. Seeing as it is a hack anyway, I'm looking for
> more guidance and a better approach.
>
> Is there any material out there that covers this specific use case? Is
> anyone interested in providing some direct help that I would then turn
> into a public article or tutorial? My company is desperate to get this
> working in a "clean" way and want to contribute something back to the
> community if we can reach that goal.
>
> Thanks in advance,
> Eric
Re: Headless build an update site with multiple features [message #590730 is a reply to message #42183] Thu, 29 January 2009 19:36 Go to previous message
Miles Parker is currently offline Miles ParkerFriend
Messages: 1341
Registered: July 2009
Senior Member
Coincidently, I'm in the same quandry, Eric.

First, it seemed relativly simple to get the build working with
multiple features. Just take the off the shelf templates and in
allElements.xml replace:

<target name="allElementsDelegator">
<ant antfile="${genericTargets}" target="${target}">
<property name="type" value="${topLevelElementType}" />
<property name="id" value="${topLevelElementId}" />
</ant>
</target>

with:

<target name="allElementsDelegator">
<ant antfile="${genericTargets}" target="${target}">
<property name="type" value="feature" />
<property name="id" value="my.great.feature" />
</ant>
<ant antfile="${genericTargets}" target="${target}">
<property name="type" value="feature" />
<property name="id" value="another.great.feature" />
</ant>
...
</target>

All of my features and plugins then get built into an update site. But
I was confused because build.properties seems to want to specify one
and only one feature.

I thought that that might have been causing related issues, so instead
I'VE created an overall feature that simply includes all of the
features I want. (I gather from an earlier posting that I can make that
feature invisible by not including feature.xml in the build.properties.)

But now I'm stuck on a couple of other issues -- I'll put in anothe
post to avoid confusion..


On 2009-01-23 09:36:44 -0800, Eric Rizzo <eclipse-news@rizzoweb.com> said:

> I've seen many examples, articles, blogs, etc. about using PDE headless
> build and some of them even talk a little about building an update site
> headlessly. But what I can't seem to find is any help in building an
> update site that includes multiple features, which may or may not all
> change at the same time.
> We have a current update site build that is a hack-job customization of
> PDE Build, but it was done under the assumption of a single feature.
> Now that we are offering multiple features, what we have won't work
> without major changes. Seeing as it is a hack anyway, I'm looking for
> more guidance and a better approach.
>
> Is there any material out there that covers this specific use case? Is
> anyone interested in providing some direct help that I would then turn
> into a public article or tutorial? My company is desperate to get this
> working in a "clean" way and want to contribute something back to the
> community if we can reach that goal.
>
> Thanks in advance,
> Eric
Previous Topic:Problem : Indirect referenced from required .class files
Next Topic:PDE Build, P2 metadata: qualifiers for features missing..
Goto Forum:
  


Current Time: Thu Jul 29 11:34:05 GMT 2021

Powered by FUDForum. Page generated in 0.01749 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top