| Strategy for locale fragments [message #1153403] |
Thu, 24 October 2013 11:38 |
 Axel Guckelsberger
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
Hi all,
currently I am attempting to build a feature containing only locale
fragments using Bucky using a Jenkins job.
The error I am getting is:
Error: file /...org.example.helloworld.nl1.de/META-INF/MANIFEST.MF, line 6:
Host bundle 'org.example.helloworld' cannot be resolved
My questions about this:
1. My current approach for that is having all locale fragments in a separate
feature, following the separation of concerns principle (first some jobs
build component features, then locales are built similarly before finally
the product builds use all created p2 repositories). If I remember correctly
fragments are not own bundles, but are just merged into their host bundle
during the build. Is it possible at all to build fragments in a separate
"locales" feature?
2. If a separate feature is possible: how should the host plug-ins be
provided? First I tried to provide the binary plug-ins as p2 repositories
created in other Jenkins jobs (the p2 repositories do not contain source
bundles). Then I tried referencing directories containing the sources as a
local reader in the rmap file. But the error shown above persists.
3. If a separate feature is possible: would this include all the host
bundles, too? My guess would be no because the feature just _depends_ on
these, it does not include them. If all host bundles would be included then
I could also remove the separate job and add building the fragments to the
job which is repsonsible for the actual product builds.
4. If a separate feature is not possible: what is best practice here? Must
all locale fragments become part of the corresponding component feature
builds/jobs creating the p2 repositories mentioned in question 2?
Thanks for your help,
Axel
[Updated on: Thu, 24 October 2013 11:42] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.04692 seconds
] 
Search
Help
Register
Login
Home
