Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Populating the build directory for an RCP Application
Populating the build directory for an RCP Application [message #42779] Tue, 27 January 2009 14:00
Rich Scott is currently offline Rich ScottFriend
Messages: 63
Registered: July 2009
I have been able to setup a basic PDE build for an RCP feature based
product. I want to be able to use a current workspace as the source for
the features and plugins needed for the build. I would like the build
script to operate similar to the product export wizard, using the product
contents to drive the build process. All of the examples that I have found
simply copy the needed plugin and feature projects from the workspace;
either manually or by explicitly listing the projects to copy in a
controlling ant script. Since the list of the required features and
plugins is already maintained within the .product, feature.xml, and
plugin.xml files I hate to have to maintain a duplicate of the content
requirements in a build file.

When I build for SVN, I use buckminster to materialize all of the required
projects from the SVN repository, which uses the product contents to drive
the materialize process.

Any suggestions on the best practice for populating the build directory
from a workspace?

I have tried using the "COPY" map file construct, to copy the projects
from the workspace. However, when I do this, the fetch step fail because
it wants to copy org.eclipse.rcp (included feature in my feature). If the
map does not include org.eclipse.rcp I get the following error:

[eclipse.fetch] Missing directory entry: feature@org.eclipse.rcp.
[eclipse.fetch] feature@org.eclipse.rcp has not be fetched.

If I add an entry to the map to COPY org.eclipse.rcp from the target
platform the error changes to

Could not retrieve feature.xml or for feature

The map entry I added was

feature@org.eclipse.rcp =COPY,../../RCPPlatformTarget/eclipse,features/org.eclipse.r cp_3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341

I also tried without including the version.

Of course the map file approach still suffers from having to maintain
duplicate lists of the required features and plugins.

My fall back is to write an ant task to parse the product and feature
definitions and copy any corresponding projects to the proper build
directory location. A simplifying fact is that all plugin and feature
project names match the plugin/feature id.
Previous Topic:Select a file in package explorer
Next Topic:Populating the build directory for an RCP Application
Goto Forum:

Current Time: Sun Jun 20 23:28:16 GMT 2021

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

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

Back to the top