| [PDE build] Headless feature where all bundles are already built fails [message #1014191] |
Mon, 25 February 2013 10:32 |
 Daniel Krügler
Messages: 853
Registered: July 2009 |
Senior Member |
|
|
Hello,
Does a PDE feature-built require bundles that need to be built?
I'm using a headless feature built to create a zip artifact that can be
used to add a feature-based plugin set to a p2 repository. Adding the
result of such a feature built to a p2 repo is no problem, but I have
changed our build process so that all bundles referenced in the feature
are separately built and I only want to create a zip that contains an
"embracing" feature and these bundles with the proper version numbers
(which are 0.0.0 in the "raw" feature.xml). I thought I could do that
with a headless pde feature build with simply an empty plugins folder,
but I'm always getting an error:
Buildfile: /some_path/rcp-build\target\features\my.feature\build.xml
does not exist
The build file mentioned here is the one that would be automatically
created by the PDE build *after* the successful build of the manually
provided
Buildfile:
/some_path/rcp-build\target\features\my.feature\target\pdeBuilder\build.xml
and this correctly happens, if I would add the bundle sources in the
plugins folder. But - as described above - now I'm having already
created my bundle jars and don't want to build them again. I simple
provide them in the baseLocation where all binary build dependencies are
located.
I thought it would help to copy the already build bundle.jars into the
plugins folder of the pde build instead, but this does not change the
error quality.
Is this a fundamental limitation of the PDE build? Or is there some way
to realize this approach? I'm wondering, because the corresponding
PDE-product-build works well without any bundles to be built.
Thanks and Greetings from Bremen,
Daniel Krügler
|
|
|
Powered by
FUDForum. Page generated in 0.02971 seconds
] 
Search
Help
Register
Login
Home
