|
Re: Aggregated repository - allow updates of mapped features [message #884723 is a reply to message #884672] |
Mon, 11 June 2012 17:22 |
|
Hi Pavel,
It's unclear to me what "it doesn't work" means. What exactly are the problems you're facing? What is it that doesn't
work? And does everything work when you open the model and re-build?
- thomas
On 06/11/2012 05:34 PM, Pavel Tarasenko wrote:
> Hi all!
>
> I have difficulties configuring aggregated repository that should serve as a central Eclipse update mirror for our team.
> We are trying to mirror ~25 external Eclipse update sites (standard set, findbugs, etc.) and also want to aggregate few
> our internal update sites where our developers are publishing Eclipse extensions they are working on.
>
> The goal is to avoid mirroring of internal update sites and have a single aggregate repository that will "redirect"
> clients to internal update sites. Any update (new plug-in version, etc.) on the internal update sites should be
> instantly and automatically available through the aggregated repository.
>
> So far, it doesn't work. I have to manually open b3 model and re-build aggregated repository to make updates from
> internal update sites avaialble in the aggregated repo.
>
> Here's details about my current setup:
> * All features from internal update sites are mapped to a custom category
> * "mirror = false" for "validated repository" entries associated with internal update sites
> * Generated final/aggregate/ directory doesn't contain mirrored artifacts from internal sites
> * compositeArtifacts.xml contains <child/> entry for each referenced internal update site
> * content.xml contains two kinds of information about our custom plug-ins and features
> ** fixed versions that were available at time of aggregate repository generation
> ** version ranges for feature declared in custom category
>
> I tried both to specify a "permissive" OSGI version range for features and keep this version range open-ended (default
> setting) but no luck. Updated version of features are perfectly avaialbe when you chek internal update site directly but
> not from aggregated repository.
>
> I'd be very grateful if someone could give me a hint what is wrong with my current configuration.
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09663 seconds