The idea is to define one URL to a p2 repository and within a CQuery I
write down a list of possible branches. A part of the URL will then be
replaced by every entry from the list. As it is done with a SVN-Provider
and a list of branches and tags.

I'm looking for that because we create a p2 repository for every
release. And if we have to list all these p2 repositories in a RMap the
RMap will grow to large.

One idea is that you combine all your repositories in a composite repository and then have our RMAP reference that.

- thomas

On 09/11/2010 07:53 PM, Matthias Kappeller wrote:
> Hi,
>
> my question is about multiple p2 repositories in a RMap.
>
> The idea is to define one URL to a p2 repository and within a CQuery I
> write down a list of possible branches. A part of the URL will then be
> replaced by every entry from the list. As it is done with a SVN-Provider
> and a list of branches and tags.
>
> I'm looking for that because we create a p2 repository for every
> release. And if we have to list all these p2 repositories in a RMap the
> RMap will grow to large.
>
> Does anybody have an idea for that?
>
> Thanks for helping...
>
> regards,
> Matthias

I've thought about that. My problem is, we do not rest upon the
osgi-version :(

regards,
Matthias

Am 12.09.10 03:37, schrieb Thomas Hallgren:
> Hi Mattias,
>
> One idea is that you combine all your repositories in a composite
> repository and then have our RMAP reference that.
>
> - thomas
>
> On 09/11/2010 07:53 PM, Matthias Kappeller wrote:
>> Hi,
>>
>> my question is about multiple p2 repositories in a RMap.
>>
>> The idea is to define one URL to a p2 repository and within a CQuery I
>> write down a list of possible branches. A part of the URL will then be
>> replaced by every entry from the list. As it is done with a SVN-Provider
>> and a list of branches and tags.
>>
>> I'm looking for that because we create a p2 repository for every
>> release. And if we have to list all these p2 repositories in a RMap the
>> RMap will grow to large.
>>
>> Does anybody have an idea for that?
>>
>> Thanks for helping...
>>
>> regards,
>> Matthias
>

On 09/12/2010 09:05 AM, Matthias Kappeller wrote:
> Hi Thomas,
>
> I've thought about that. My problem is, we do not rest upon the
> osgi-version :(
>
Not sure why that would change the circumstances in this case. Can you elaborate?

- thomas

> regards,
> Matthias
>
>
> Am 12.09.10 03:37, schrieb Thomas Hallgren:
>> Hi Mattias,
>>
>> One idea is that you combine all your repositories in a composite
>> repository and then have our RMAP reference that.
>>
>> - thomas
>>
>> On 09/11/2010 07:53 PM, Matthias Kappeller wrote:
>>> Hi,
>>>
>>> my question is about multiple p2 repositories in a RMap.
>>>
>>> The idea is to define one URL to a p2 repository and within a CQuery I
>>> write down a list of possible branches. A part of the URL will then be
>>> replaced by every entry from the list. As it is done with a SVN-Provider
>>> and a list of branches and tags.
>>>
>>> I'm looking for that because we create a p2 repository for every
>>> release. And if we have to list all these p2 repositories in a RMap the
>>> RMap will grow to large.
>>>
>>> Does anybody have an idea for that?
>>>
>>> Thanks for helping...
>>>
>>> regards,
>>> Matthias
>>
>

Am 12.09.10 11:40, schrieb Thomas Hallgren:
> On 09/12/2010 09:05 AM, Matthias Kappeller wrote:
>> Hi Thomas,
>>
>> I've thought about that. My problem is, we do not rest upon the
>> osgi-version :(
>>
> Not sure why that would change the circumstances in this case. Can you
> elaborate?
I think a example will show what i meant:
Two Bundles (A) and (B), both have the version 1.0.0
(A) has a dependency to (B)
Within a release build both bundles - (A)_1.0.0.release1 and
(B)_1.0.0.release1 - will end up in a repository named [release_1]
Now (B) will be changed in an incompatible way so also (A) has to be
changed - BUT we do not change the OSGi versions! (unfortunately :( )
Another release build and the bundles - (A)_1.0.0.release2 and
(B)_1.0.0.release2 - end up in a repository named [release_2]

So if I will get (A) from [release_1] i also have to get (B) from
[release_1].

I think we will run into a problem if we put both repositories into a
composite because:
When i create a CQuery to get (A)_1.0.0.release1, I will also get the
newest from (B) with version 1.0.0 this will be (B)_1.0.0.release2. But
they are not compatible.

Am i right?

>
> - thomas
>
>> regards,
>> Matthias
>>
>>
>> Am 12.09.10 03:37, schrieb Thomas Hallgren:
>>> Hi Mattias,
>>>
>>> One idea is that you combine all your repositories in a composite
>>> repository and then have our RMAP reference that.
>>>
>>> - thomas
>>>
>>> On 09/11/2010 07:53 PM, Matthias Kappeller wrote:
>>>> Hi,
>>>>
>>>> my question is about multiple p2 repositories in a RMap.
>>>>
>>>> The idea is to define one URL to a p2 repository and within a CQuery I
>>>> write down a list of possible branches. A part of the URL will then be
>>>> replaced by every entry from the list. As it is done with a
>>>> SVN-Provider
>>>> and a list of branches and tags.
>>>>
>>>> I'm looking for that because we create a p2 repository for every
>>>> release. And if we have to list all these p2 repositories in a RMap the
>>>> RMap will grow to large.
>>>>
>>>> Does anybody have an idea for that?
>>>>
>>>> Thanks for helping...
>>>>
>>>> regards,
>>>> Matthias
>>>
>>
>

Not changing the versions does of course create problems. It actually
violates the whole p2 logic since an installable unit is uniquely
identified by its name and version (this combination should be
considered immutable). So you're right, a composite won't work for you.

- thomas

On 09/12/2010 09:18 PM, Matthias Kappeller wrote:
> Am 12.09.10 11:40, schrieb Thomas Hallgren:
>> On 09/12/2010 09:05 AM, Matthias Kappeller wrote:
>>> Hi Thomas,
>>>
>>> I've thought about that. My problem is, we do not rest upon the
>>> osgi-version :(
>>>
>> Not sure why that would change the circumstances in this case. Can you
>> elaborate?
> I think a example will show what i meant:
> Two Bundles (A) and (B), both have the version 1.0.0
> (A) has a dependency to (B)
> Within a release build both bundles - (A)_1.0.0.release1 and
> (B)_1.0.0.release1 - will end up in a repository named [release_1]
> Now (B) will be changed in an incompatible way so also (A) has to be
> changed - BUT we do not change the OSGi versions! (unfortunately :( )
> Another release build and the bundles - (A)_1.0.0.release2 and
> (B)_1.0.0.release2 - end up in a repository named [release_2]
>
> So if I will get (A) from [release_1] i also have to get (B) from
> [release_1].
>
> I think we will run into a problem if we put both repositories into a
> composite because:
> When i create a CQuery to get (A)_1.0.0.release1, I will also get the
> newest from (B) with version 1.0.0 this will be (B)_1.0.0.release2. But
> they are not compatible.
>
> Am i right?
>
>>
>> - thomas
>>
>>> regards,
>>> Matthias
>>>
>>>
>>> Am 12.09.10 03:37, schrieb Thomas Hallgren:
>>>> Hi Mattias,
>>>>
>>>> One idea is that you combine all your repositories in a composite
>>>> repository and then have our RMAP reference that.
>>>>
>>>> - thomas
>>>>
>>>> On 09/11/2010 07:53 PM, Matthias Kappeller wrote:
>>>>> Hi,
>>>>>
>>>>> my question is about multiple p2 repositories in a RMap.
>>>>>
>>>>> The idea is to define one URL to a p2 repository and within a CQuery I
>>>>> write down a list of possible branches. A part of the URL will then be
>>>>> replaced by every entry from the list. As it is done with a
>>>>> SVN-Provider
>>>>> and a list of branches and tags.
>>>>>
>>>>> I'm looking for that because we create a p2 repository for every
>>>>> release. And if we have to list all these p2 repositories in a RMap
>>>>> the
>>>>> RMap will grow to large.
>>>>>
>>>>> Does anybody have an idea for that?
>>>>>
>>>>> Thanks for helping...
>>>>>
>>>>> regards,
>>>>> Matthias
>>>>
>>>
>>
>