Temporary Repo Locationhttps://www.eclipse.org/forums/index.php/mv/msg/175161/557990/#msg_557990
I'm wondering if there is a way to temporarily register a repository with
the update manager.

I know I can use the IMetadataRepositoryManager and
IArtifactRepositoryManager to add repositories to the system permantently.
I'm looking for a way to add a repository location in such a way that it is
not persisted when the application shuts down.

Here's why:
I have a number of servers that are automatically detected by the system.
These servers frequently appear, disappear, and change their addresses.
Each time the application runs, it may be able to reach a completely
different set of servers.

I'm allowing each server to register itself as the host of a repository
while it is detected by my application but I would like to remove the
repository from the list when the server is no longer available. The best
way me to keep the repository list clean would be to re-add the repositories
each time the application launches.

Any help would be appreciated.

Thanks,

James]]>James Peltzer2010-09-09T17:26:52-00:00Re: Temporary Repo Locationhttps://www.eclipse.org/forums/index.php/mv/msg/175161/558184/#msg_558184
of that repository would pick up the changes in the contained repositories.

This way, you would only need to add your dynamic repository once.

Regards
- henrik

On 9/9/10 7:26 PM, James Peltzer wrote:
> Hi all,
> I'm wondering if there is a way to temporarily register a repository
> with the update manager.
>
> I know I can use the IMetadataRepositoryManager and
> IArtifactRepositoryManager to add repositories to the system
> permantently. I'm looking for a way to add a repository location in such
> a way that it is not persisted when the application shuts down.
>
> Here's why:
> I have a number of servers that are automatically detected by the
> system. These servers frequently appear, disappear, and change their
> addresses. Each time the application runs, it may be able to reach a
> completely different set of servers.
>
> I'm allowing each server to register itself as the host of a repository
> while it is detected by my application but I would like to remove the
> repository from the list when the server is no longer available. The
> best way me to keep the repository list clean would be to re-add the
> repositories each time the application launches.
>
> Any help would be appreciated.
>
> Thanks,
>
> James
>
>
>
>]]>Henrik Lindberg2010-09-10T12:56:17-00:00Re: Temporary Repo Locationhttps://www.eclipse.org/forums/index.php/mv/msg/175161/576222/#msg_576222
of that repository would pick up the changes in the contained repositories.

This way, you would only need to add your dynamic repository once.

Regards
- henrik

On 9/9/10 7:26 PM, James Peltzer wrote:
> Hi all,
> I'm wondering if there is a way to temporarily register a repository
> with the update manager.
>
> I know I can use the IMetadataRepositoryManager and
> IArtifactRepositoryManager to add repositories to the system
> permantently. I'm looking for a way to add a repository location in such
> a way that it is not persisted when the application shuts down.
>
> Here's why:
> I have a number of servers that are automatically detected by the
> system. These servers frequently appear, disappear, and change their
> addresses. Each time the application runs, it may be able to reach a
> completely different set of servers.
>
> I'm allowing each server to register itself as the host of a repository
> while it is detected by my application but I would like to remove the
> repository from the list when the server is no longer available. The
> best way me to keep the repository list clean would be to re-add the
> repositories each time the application launches.
>
> Any help would be appreciated.
>
> Thanks,
>
> James
>
>
>
>]]>Henrik Lindberg2010-09-10T12:56:17-00:00Re: Temporary Repo Locationhttps://www.eclipse.org/forums/index.php/mv/msg/175161/631706/#msg_631706
repository even though an in-memory repository makes more sense in my mind.
The only remaining issue with this approach is that I can't seem to nest
composite repositories. That is, if the repository I'm trying to link to
from my composite repository is also a composite, it doesn't seem to work.
Is this actually the case? Is there a way to nest the composite?

Thanks again,

James

"Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote in message
news:i6d9ti$h2l$1@build.eclipse.org...
> Have you looked at using a composite repository? Thinking that a refresh
> of that repository would pick up the changes in the contained
> repositories.
>
> This way, you would only need to add your dynamic repository once.
>
> Regards
> - henrik
>
> On 9/9/10 7:26 PM, James Peltzer wrote:
>> Hi all,
>> I'm wondering if there is a way to temporarily register a repository
>> with the update manager.
>>
>> I know I can use the IMetadataRepositoryManager and
>> IArtifactRepositoryManager to add repositories to the system
>> permantently. I'm looking for a way to add a repository location in such
>> a way that it is not persisted when the application shuts down.
>>
>> Here's why:
>> I have a number of servers that are automatically detected by the
>> system. These servers frequently appear, disappear, and change their
>> addresses. Each time the application runs, it may be able to reach a
>> completely different set of servers.
>>
>> I'm allowing each server to register itself as the host of a repository
>> while it is detected by my application but I would like to remove the
>> repository from the list when the server is no longer available. The
>> best way me to keep the repository list clean would be to re-add the
>> repositories each time the application launches.
>>
>> Any help would be appreciated.
>>
>> Thanks,
>>
>> James
>>
>>
>>
>>
>
>]]>James Peltzer2010-10-08T13:55:46-00:00Re: Temporary Repo Locationhttps://www.eclipse.org/forums/index.php/mv/msg/175161/631763/#msg_631763
One potential issue is if a repository changes type and was visitied by
clients - I seem to recall that there were issues with that - clients
may hold on to their belief the site is still in the old form.

I assume you have checked that the composite site is does not have a non
composite index, or that it is an old style update site at the same time.

To make sure it is not a caching issue like this, I would make sure to
start with a clean slate to make sure.

Regards
- henrik

On 10/8/10 3:55 PM, James Peltzer wrote:
> Thanks for the reply. I have gone the route of making a composite
> repository even though an in-memory repository makes more sense in my
> mind. The only remaining issue with this approach is that I can't seem
> to nest composite repositories. That is, if the repository I'm trying to
> link to from my composite repository is also a composite, it doesn't
> seem to work. Is this actually the case? Is there a way to nest the
> composite?
>]]>Henrik Lindberg2010-10-08T15:28:23-00:00