Re: [Pluginbuilder-development] Pluginbuilder experiences

[Markus B. <Mar...@gm...>]

> One question is: what's the level of p2 support in PluginBuilder 0.6.0?
> The release notes state that it's supported, but it's necessary to
> delete postBuild.xml.
hm, as far is I remember the deletion of postBuild.xml was related to
the pre-p2 update site. Pluginbuilder 0.6.0 does not support p2. But
it is quite easy to create a p2 repository since the PDE provides a
couple of p2 related properties:
http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_metadata_generator.html
The properties are already included in the Pluginbuilder nightly and
can be set via the Properties tab of the Pluginbuilder Editor.
>
> Also: as I understand p2, it's necessary to run the p2 Director task.
> Having PluginBuilder (or something - dare I suggest the PDE...) set up
> something that works would be great.
Have a look at http://rcpsample-3-4.pluginbuilder.org/nightly/p2-updateSite/
which has been set up with the pluginbuilder nightly.
Still unclear: how to set a category,
https://sourceforge.net/forum/message.php?msg_id=6025032.

> (I tried for ages to get this right - but apparently one needs to be a
> Mensa member and infinite patience to get even the most trivial things
> to work with the PDE Build).
I would not blame PDE for that. I think it is intrinsic to all build
related development because it takes so long to get feedback. That is
the difference between developing code where you get immediate
feedback from your test suites as opposed to developing build scripts
where you have to wait minutes or even hours to see results. So, one
of the principles of writing build scripts should be to make them as
modular as possible and reduce time to feedback. For example it should
be possible to re-run the tests without doing all the compilation
steps before.

Markus