|Re: [cross-project-issues-dev] Juno rt contribution|
Am 15.03.2012 18:50, schrieb Borislav Kapukaranov:
> All my features and product are marked with the "magic iu" for RT features.I suggest that you only tag the "Target Components" feature with the
magic IU. That should be the only feature that is "visible"
(categorized) in the Juno repository.
All other features (including your product) do not need to have the
"magic iu". They are usually not categorized/visible in Juno repository.
However, you can make them visible and categorize them in your repo as
Thus, when installing using the director you usually don't pick the
"Target Components" feature. It should work then.
In the case of RT it's usually just a "Target Components" feature.
> 1. Can we contribute p2 products or just features are accepted?
You have to include them in your product and either mirror them into
> 2. Is the Orbit p2 repo aggregated in the Juno repo - I couldn't find
> some of my required dependencies until I added the Orbit repo along with
> the Juno one to my composite p2 repository?
your repo or reference Orbit.
Same as with Orbit. I mirror them into my project repo because I don't
> What is the standard procedure in this case, should I package these
> bundles with my features?
reference the Equinox repo in my composite repo. But that may be the
better option (in terms of disc space duplication).
cross-project-issues-dev mailing list
Back to the top