| P2 PDE Headless Build: Feature repo getting too many plugins [message #606500] |
Tue, 24 August 2010 15:59 |
 James Peltzer
Messages: 43
Registered: July 2009 |
Member |
|
|
Hey all,
BACKGROUND:
I have had to divide my product up into a main 'framework' product (which
gets its own repository, exe, config.ini, etc.) and several features. Each
feature needs to be built separately and packaged into its own p2
repository.
In the end, we will be having our users install the framework product and
then use the p2 director to add certain extra features (or just have them
extract them to the dropins directory).
HOW I'M USING THE HEADLESS BUILD:
My dev environment copies everything (the framework and the extra features)
from my workspace to a separate build location divided into plugins and
features directories. First, I run the headless product build to get my
framework, then I use different build.properties files to go through each
extra feature run a headless feature build (topLevelElementType=feature,
topLevelElementId=[feature ID], repoBaseLocation=[location of framework
repo]).
WHAT'S HAPPENING:
The repositories for the extra features not only include the plugins I tell
the feature to include, but also include the dependencies that I don't
'include' in the feature.xml. I don't want this; the dependencies are
already in the platform repository. This causes my generated repositories
to be much MUCH bigger than they should be (and causes duplicate plug-ins
when I'm using the drop-ins install).
WHAT ELSE I KNOW:
I get the correct repository when I do a feature export from the Eclipse
IDE.
If I take the plug-ins and features for the extra feature and put them in
their own separate build directory, I get the correct output.
So, how can I get the correct output when I just want to make a
build.properties file and point it at the copy of the entire workspace?
Any help would be greatly appreciated.
Thanks,
James
|
|
|
Powered by
FUDForum. Page generated in 0.03595 seconds