Eclipse Community Forums: Rich Client Platform (RCP) » build.xml is deleted after exporting plugin

Home » Eclipse Projects » Rich Client Platform (RCP) » build.xml is deleted after exporting plugin

build.xml is deleted after exporting plugin [message #444339]

Tue, 14 February 2006 01:35

Eclipse User

Originally posted by: glenn.janet.co.jp

This problem has been going on for a while now.
I use Ant to build my jars.

The problem is, after I export an RCP project that contains
a build.xml Ant script, the build.xml is deleted. Why?

Re: build.xml is deleted after exporting plugin [message #444377 is a reply to message #444339]

Tue, 14 February 2006 12:53

Eclipse User

Have you marked it in the Build tab (of the build.properties/manifest.mf/plugin.xml editor) that it's a custom build?

(the entry it writes to in the build.properties is 'custom=true' if you want to add it yourself)

If not, when you build it, PDE generates a build.xml (which will overwrite yours) and deletes it when it's finished. You could of course call it something else if you wanted, in which case you wouldn't see this behaviour.

If this is what's happening, I'd suggest filing a bug of unfriendly behaviour, and recommend that when running, if it finds a build.xml, it doesn't auto-generate/delete it afterwards.

I've just verified that this is ineeded what happens if you don't have custom build selected. If you do have the build.xml, you must get it to define certain targets (e.g. build.jars) in order for it to co-exist peacefully with the Eclipse concept.

Alex.

Re: build.xml is deleted after exporting plugin [message #444381 is a reply to message #444377]

Tue, 14 February 2006 15:11

Eclipse User

Originally posted by: cfieber.gmail.com

Alex Blewitt wrote:
>
> I've just verified that this is ineeded what happens if you don't have custom build selected. If you do have the build.xml, you must get it to define certain targets (e.g. build.jars) in order for it to co-exist peacefully with the Eclipse concept.

The exact targets you have to define are:

build.jars

gather.bin.parts

gather.logs

Of those targets, the one I've hooked into is gather.bin.parts. When
this target is called, the property 'destination.temp.folder' is set.
After this target runs, if you have created a folder called
${destination.temp.folder}/<Bundle-SymbolicName>_<Bundle-Version > and
filled it will the classes and resources for your plugin jar, it will
create the plugin jar (including signing if you've chosen that) in the
export directory.

The main downside is accessing the Bundle-SymbolicName and
Bundle-Version attributes. I set the project name attribute to the
Bundle-Symbolic name (needed for other stuff in my build setup anyway),
and set the plugin version as a property in build.properties (dirty,
I'll likely build / find a task to read it out of the Manifest file
directly).

I don't do anything in build.jars or gather.logs.

Regards,

-Cameron

Previous Topic:	Feature based products
Next Topic:	exporting feature-based rcp product - help!

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 14 16:03:47 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter