Home » Archived » B3 » B3 Aggregator + Helios Site
| B3 Aggregator + Helios Site [message #535450] |
Sun, 23 May 2010 17:24  |
|
Hello
Obviously, B3 aggregator is used to assemble the Helios milestone site.
I try to mirror the entire Helios site using B3 aggregator and I often
run into problems during the validation phase.
Why can't I mirror the Helios site using the B3 aggregator but the
entire thing was created using the same program running the same
validations? How can the site be assembled successfully if there
are invalid constraints preventing the mirroring?
Besides that, I found that it is very temporal whether mirroring is
possible or not:
- today = validation error in the gmf.examples area
- Sat a week ago = validation error in the xtext area
- Tue a week ago = mirroring possible
- Sat 2 weeks ago = validation error in the modisco area
....
What's up?
Michael
|
|
| |
| Re: B3 Aggregator + Helios Site [message #535465 is a reply to message #535457] |
Sun, 23 May 2010 20:23  |
|
I think the main reason is that what you find at releases/helios is an aggregate that contains older versions along with
the new ones. The b3 aggregator creates a repository that is validated. The composite however, is several such
repositories. Put together, they no longer represent a 100% coherent repository.
- thomas
On 05/23/2010 08:00 PM, Henrik Lindberg wrote:
> A very possible reason is that there are actual errors in the input.
>
> Helios is a moving target, and as Dave Williams can testify there is
> almost always some contributor that has some problem/conflict.
>
> These issues are gradually solved until a release ready Helios site is
> produced.
>
> I don't know if good helios repos are kept somewhere.
>
> - henrik
>
> On 5/23/10 7:24 PM, Michael Pellaton wrote:
>> Hello
>>
>> Obviously, B3 aggregator is used to assemble the Helios milestone site.
>>
>> I try to mirror the entire Helios site using B3 aggregator and I often
>> run into problems during the validation phase.
>>
>> Why can't I mirror the Helios site using the B3 aggregator but the
>> entire thing was created using the same program running the same
>> validations? How can the site be assembled successfully if there
>> are invalid constraints preventing the mirroring?
>>
>> Besides that, I found that it is very temporal whether mirroring is
>> possible or not:
>> - today = validation error in the gmf.examples area
>> - Sat a week ago = validation error in the xtext area
>> - Tue a week ago = mirroring possible
>> - Sat 2 weeks ago = validation error in the modisco area
>> ...
>>
>> What's up?
>>
>>
>> Michael
>
|
|
|
| Re: B3 Aggregator + Helios Site [message #535469 is a reply to message #535465] |
Sun, 23 May 2010 21:04 |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
So, how should someone that wants to use Helios repo in their own
aggregation work around this issue?
- henrik
On 5/23/10 10:23 PM, Thomas Hallgren wrote:
> I think the main reason is that what you find at releases/helios is an
> aggregate that contains older versions along with the new ones. The b3
> aggregator creates a repository that is validated. The composite
> however, is several such repositories. Put together, they no longer
> represent a 100% coherent repository.
>
> - thomas
>
> On 05/23/2010 08:00 PM, Henrik Lindberg wrote:
>> A very possible reason is that there are actual errors in the input.
>>
>> Helios is a moving target, and as Dave Williams can testify there is
>> almost always some contributor that has some problem/conflict.
>>
>> These issues are gradually solved until a release ready Helios site is
>> produced.
>>
>> I don't know if good helios repos are kept somewhere.
>>
>> - henrik
>>
>> On 5/23/10 7:24 PM, Michael Pellaton wrote:
>>> Hello
>>>
>>> Obviously, B3 aggregator is used to assemble the Helios milestone site.
>>>
>>> I try to mirror the entire Helios site using B3 aggregator and I often
>>> run into problems during the validation phase.
>>>
>>> Why can't I mirror the Helios site using the B3 aggregator but the
>>> entire thing was created using the same program running the same
>>> validations? How can the site be assembled successfully if there
>>> are invalid constraints preventing the mirroring?
>>>
>>> Besides that, I found that it is very temporal whether mirroring is
>>> possible or not:
>>> - today = validation error in the gmf.examples area
>>> - Sat a week ago = validation error in the xtext area
>>> - Tue a week ago = mirroring possible
>>> - Sat 2 weeks ago = validation error in the modisco area
>>> ...
>>>
>>> What's up?
>>>
>>>
>>> Michael
>>
>
|
|
|
| Re: B3 Aggregator + Helios Site [message #535470 is a reply to message #535469] |
Sun, 23 May 2010 21:46 |
|
Well, one solution is to use the p2 mirrorApplication, but that's not my
favourite solution as this seems to be more or less a wget for repos.
A cool feature for the b3 aggregator would be to mirror only the newest
artifacts without having to specify version constraints for each IU
(similar to the p2 install dialog where one can hide old versions).
Another help would be regex exclusions for IUs (e.g. exclude *javahl*
instead of 12 IUs containing javahl).
Michael
On 05/23/2010 11:04 PM, Henrik Lindberg wrote:
> So, how should someone that wants to use Helios repo in their own
> aggregation work around this issue?
>
> - henrik
>
> On 5/23/10 10:23 PM, Thomas Hallgren wrote:
>> I think the main reason is that what you find at releases/helios is an
>> aggregate that contains older versions along with the new ones. The b3
>> aggregator creates a repository that is validated. The composite
>> however, is several such repositories. Put together, they no longer
>> represent a 100% coherent repository.
>>
>> - thomas
>>
>> On 05/23/2010 08:00 PM, Henrik Lindberg wrote:
>>> A very possible reason is that there are actual errors in the input.
>>>
>>> Helios is a moving target, and as Dave Williams can testify there is
>>> almost always some contributor that has some problem/conflict.
>>>
>>> These issues are gradually solved until a release ready Helios site is
>>> produced.
>>>
>>> I don't know if good helios repos are kept somewhere.
>>>
>>> - henrik
>>>
>>> On 5/23/10 7:24 PM, Michael Pellaton wrote:
>>>> Hello
>>>>
>>>> Obviously, B3 aggregator is used to assemble the Helios milestone site.
>>>>
>>>> I try to mirror the entire Helios site using B3 aggregator and I often
>>>> run into problems during the validation phase.
>>>>
>>>> Why can't I mirror the Helios site using the B3 aggregator but the
>>>> entire thing was created using the same program running the same
>>>> validations? How can the site be assembled successfully if there
>>>> are invalid constraints preventing the mirroring?
>>>>
>>>> Besides that, I found that it is very temporal whether mirroring is
>>>> possible or not:
>>>> - today = validation error in the gmf.examples area
>>>> - Sat a week ago = validation error in the xtext area
>>>> - Tue a week ago = mirroring possible
>>>> - Sat 2 weeks ago = validation error in the modisco area
>>>> ...
>>>>
>>>> What's up?
>>>>
>>>>
>>>> Michael
>>>
>>
>
|
|
|
| Re: B3 Aggregator + Helios Site [message #535478 is a reply to message #535470] |
Mon, 24 May 2010 00:56 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Using filters is something that has been discussed - esp. "include only
latest". Not sure if an issue was logged for that...
- henrik
On 5/23/10 11:46 PM, Michael Pellaton wrote:
> Well, one solution is to use the p2 mirrorApplication, but that's not my
> favourite solution as this seems to be more or less a wget for repos.
>
> A cool feature for the b3 aggregator would be to mirror only the newest
> artifacts without having to specify version constraints for each IU
> (similar to the p2 install dialog where one can hide old versions).
>
> Another help would be regex exclusions for IUs (e.g. exclude *javahl*
> instead of 12 IUs containing javahl).
>
> Michael
>
> On 05/23/2010 11:04 PM, Henrik Lindberg wrote:
>> So, how should someone that wants to use Helios repo in their own
>> aggregation work around this issue?
>>
>> - henrik
>>
>> On 5/23/10 10:23 PM, Thomas Hallgren wrote:
>>> I think the main reason is that what you find at releases/helios is an
>>> aggregate that contains older versions along with the new ones. The b3
>>> aggregator creates a repository that is validated. The composite
>>> however, is several such repositories. Put together, they no longer
>>> represent a 100% coherent repository.
>>>
>>> - thomas
>>>
>>> On 05/23/2010 08:00 PM, Henrik Lindberg wrote:
>>>> A very possible reason is that there are actual errors in the input.
>>>>
>>>> Helios is a moving target, and as Dave Williams can testify there is
>>>> almost always some contributor that has some problem/conflict.
>>>>
>>>> These issues are gradually solved until a release ready Helios site is
>>>> produced.
>>>>
>>>> I don't know if good helios repos are kept somewhere.
>>>>
>>>> - henrik
>>>>
>>>> On 5/23/10 7:24 PM, Michael Pellaton wrote:
>>>>> Hello
>>>>>
>>>>> Obviously, B3 aggregator is used to assemble the Helios milestone site.
>>>>>
>>>>> I try to mirror the entire Helios site using B3 aggregator and I often
>>>>> run into problems during the validation phase.
>>>>>
>>>>> Why can't I mirror the Helios site using the B3 aggregator but the
>>>>> entire thing was created using the same program running the same
>>>>> validations? How can the site be assembled successfully if there
>>>>> are invalid constraints preventing the mirroring?
>>>>>
>>>>> Besides that, I found that it is very temporal whether mirroring is
>>>>> possible or not:
>>>>> - today = validation error in the gmf.examples area
>>>>> - Sat a week ago = validation error in the xtext area
>>>>> - Tue a week ago = mirroring possible
>>>>> - Sat 2 weeks ago = validation error in the modisco area
>>>>> ...
>>>>>
>>>>> What's up?
>>>>>
>>>>>
>>>>> Michael
>>>>
>>>
>>
|
|
|
| Re: B3 Aggregator + Helios Site [message #535489 is a reply to message #535470] |
Mon, 24 May 2010 03:28 |
|
On 05/23/2010 11:46 PM, Michael Pellaton wrote:
> A cool feature for the b3 aggregator would be to mirror only the newest
> artifacts without having to specify version constraints for each IU
> (similar to the p2 install dialog where one can hide old versions).
>
It already does this. I haven't seen the errors but my guess is that they relate to features that has been removed in
newer versions.
You can always try aggregating the latest contribution to the composite, i.e.
http://download.eclipse.org/releases/helios/201005210900
- thomas
|
|
|
| Re: B3 Aggregator + Helios Site [message #535516 is a reply to message #535489] |
Mon, 24 May 2010 08:30 |
|
> You can always try aggregating the latest contribution to the composite,
> i.e.
> http://download.eclipse.org/releases/helios/201005210900
When doing that, I get
java.lang.ClassCastException:
org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
org.eclipse.core.runtime.CoreException: java.lang.ClassCastException:
org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
at org.eclipse.b3.util.ExceptionUtils.fromMessage(ExceptionUtil s.java:53)
at org.eclipse.b3.util.ExceptionUtils.wrap(ExceptionUtils.java: 120)
at
org.eclipse.b3.aggregator.engine.RepositoryVerifier.run(Repo sitoryVerifier.java:271)
at
org.eclipse.b3.aggregator.engine.Builder.runRepositoryVerifi er(Builder.java:1109)
at org.eclipse.b3.aggregator.engine.Builder.run(Builder.java:62 1)
at
org.eclipse.b3.aggregator.presentation.AggregatorActionBarCo ntributor$BuildRepoAction$1.run(AggregatorActionBarContribut or.java:267)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.ClassCastException:
org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
at
org.eclipse.b3.aggregator.engine.RepositoryVerifier.run(Repo sitoryVerifier.java:214)
... 4 more
I am using Eclipse SDK 3.6.RC2 + b3 aggregator 0.1.0.r01001
Michael
|
|
|
| Re: B3 Aggregator + Helios Site [message #535547 is a reply to message #535516] |
Mon, 24 May 2010 12:15 |
|
That sounds like a bug. Can you please try with the latest version
(unless that's what you have already) and if this problem is still
present, enter a bugzilla to Modeling/EMFT.b3/aggregator?
Thanks,
Thomas Hallgren
On 05/24/2010 10:30 AM, Michael Pellaton wrote:
>> You can always try aggregating the latest contribution to the composite,
>> i.e.
>> http://download.eclipse.org/releases/helios/201005210900
> When doing that, I get
>
> java.lang.ClassCastException:
> org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
> to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
> org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
> to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
>
> org.eclipse.core.runtime.CoreException: java.lang.ClassCastException:
> org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
> to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
> at org.eclipse.b3.util.ExceptionUtils.fromMessage(ExceptionUtil s.java:53)
> at org.eclipse.b3.util.ExceptionUtils.wrap(ExceptionUtils.java: 120)
> at
> org.eclipse.b3.aggregator.engine.RepositoryVerifier.run(Repo sitoryVerifier.java:271)
>
> at
> org.eclipse.b3.aggregator.engine.Builder.runRepositoryVerifi er(Builder.java:1109)
>
> at org.eclipse.b3.aggregator.engine.Builder.run(Builder.java:62 1)
> at
> org.eclipse.b3.aggregator.presentation.AggregatorActionBarCo ntributor$BuildRepoAction$1.run(AggregatorActionBarContribut or.java:267)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.ClassCastException:
> org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
> to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
> at
> org.eclipse.b3.aggregator.engine.RepositoryVerifier.run(Repo sitoryVerifier.java:214)
>
> ... 4 more
>
>
>
> I am using Eclipse SDK 3.6.RC2 + b3 aggregator 0.1.0.r01001
>
> Michael
|
|
| |
| Re: B3 Aggregator + Helios Site [message #542006 is a reply to message #535450] |
Wed, 23 June 2010 13:57 |
Lars Fischer
Messages: 105
Registered: July 2009 |
Senior Member |
|
|
Hello,
I tried to mirror the final helios p2 site with the b3 aggregator.
I created a .b3aggr file with one contribution, mapping the helios url:
http://download.eclipse.org/releases/helios/
Running this, I get this error:
Loading all repositories
Starting generation of composite repository
Adding child meta-data repository
http://download.eclipse.org/releases/helios
Done. Took 0 seconds
Starting generation of verification feature
Done. Took 0 seconds
Starting generation of categories
Done. Took 0 seconds
Starting planner verification
Verifying config win32,win32,x86...
Verifying config win32,win32,x86_64...
Verifying config linux,gtk,x86...
Software being installed: all.contributed.content.feature.group 1.0.0
Missing requirement for filter properties ~= $0:
org.eclipse.ecf.core.featurepatch.feature.group 3.3.0.v20100615-1452
requires 'org.eclipse.ecf.core.featurepatch.feature.jar
[3.3.0.v20100615-1452]' but it could not be found
Cannot satisfy dependency: all.contributed.content.feature.group 1.0.0
depends on: org.eclipse.ecf.core.featurepatch.feature.group 0.0.0
Where is my mistake?
Regards,
Lars
|
|
|
| Re: B3 Aggregator + Helios Site [message #542058 is a reply to message #542006] |
Wed, 23 June 2010 16:30 |
Filip Hrbek
Messages: 233
Registered: July 2009 |
Senior Member |
|
|
I created a bugzilla issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=317727
Filip
Lars Fischer wrote:
> Hello,
>
> I tried to mirror the final helios p2 site with the b3 aggregator.
>
> I created a .b3aggr file with one contribution, mapping the helios url:
> http://download.eclipse.org/releases/helios/
>
> Running this, I get this error:
>
> Loading all repositories
> Starting generation of composite repository
> Adding child meta-data repository
> http://download.eclipse.org/releases/helios
> Done. Took 0 seconds
> Starting generation of verification feature
> Done. Took 0 seconds
> Starting generation of categories
> Done. Took 0 seconds
> Starting planner verification
> Verifying config win32,win32,x86...
> Verifying config win32,win32,x86_64...
> Verifying config linux,gtk,x86...
> Software being installed: all.contributed.content.feature.group 1.0.0
> Missing requirement for filter properties ~= $0:
> org.eclipse.ecf.core.featurepatch.feature.group 3.3.0.v20100615-1452
> requires 'org.eclipse.ecf.core.featurepatch.feature.jar
> [3.3.0.v20100615-1452]' but it could not be found
> Cannot satisfy dependency: all.contributed.content.feature.group 1.0.0
> depends on: org.eclipse.ecf.core.featurepatch.feature.group 0.0.0
>
>
> Where is my mistake?
>
>
> Regards,
> Lars
>
|
|
| |
| Re: B3 Aggregator + Helios Site [message #608269 is a reply to message #535457] |
Sun, 23 May 2010 20:23 |
|
I think the main reason is that what you find at releases/helios is an aggregate that contains older versions along with
the new ones. The b3 aggregator creates a repository that is validated. The composite however, is several such
repositories. Put together, they no longer represent a 100% coherent repository.
- thomas
On 05/23/2010 08:00 PM, Henrik Lindberg wrote:
> A very possible reason is that there are actual errors in the input.
>
> Helios is a moving target, and as Dave Williams can testify there is
> almost always some contributor that has some problem/conflict.
>
> These issues are gradually solved until a release ready Helios site is
> produced.
>
> I don't know if good helios repos are kept somewhere.
>
> - henrik
>
> On 5/23/10 7:24 PM, Michael Pellaton wrote:
>> Hello
>>
>> Obviously, B3 aggregator is used to assemble the Helios milestone site.
>>
>> I try to mirror the entire Helios site using B3 aggregator and I often
>> run into problems during the validation phase.
>>
>> Why can't I mirror the Helios site using the B3 aggregator but the
>> entire thing was created using the same program running the same
>> validations? How can the site be assembled successfully if there
>> are invalid constraints preventing the mirroring?
>>
>> Besides that, I found that it is very temporal whether mirroring is
>> possible or not:
>> - today = validation error in the gmf.examples area
>> - Sat a week ago = validation error in the xtext area
>> - Tue a week ago = mirroring possible
>> - Sat 2 weeks ago = validation error in the modisco area
>> ...
>>
>> What's up?
>>
>>
>> Michael
>
|
|
|
| Re: B3 Aggregator + Helios Site [message #608271 is a reply to message #535465] |
Sun, 23 May 2010 21:04 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
So, how should someone that wants to use Helios repo in their own
aggregation work around this issue?
- henrik
On 5/23/10 10:23 PM, Thomas Hallgren wrote:
> I think the main reason is that what you find at releases/helios is an
> aggregate that contains older versions along with the new ones. The b3
> aggregator creates a repository that is validated. The composite
> however, is several such repositories. Put together, they no longer
> represent a 100% coherent repository.
>
> - thomas
>
> On 05/23/2010 08:00 PM, Henrik Lindberg wrote:
>> A very possible reason is that there are actual errors in the input.
>>
>> Helios is a moving target, and as Dave Williams can testify there is
>> almost always some contributor that has some problem/conflict.
>>
>> These issues are gradually solved until a release ready Helios site is
>> produced.
>>
>> I don't know if good helios repos are kept somewhere.
>>
>> - henrik
>>
>> On 5/23/10 7:24 PM, Michael Pellaton wrote:
>>> Hello
>>>
>>> Obviously, B3 aggregator is used to assemble the Helios milestone site.
>>>
>>> I try to mirror the entire Helios site using B3 aggregator and I often
>>> run into problems during the validation phase.
>>>
>>> Why can't I mirror the Helios site using the B3 aggregator but the
>>> entire thing was created using the same program running the same
>>> validations? How can the site be assembled successfully if there
>>> are invalid constraints preventing the mirroring?
>>>
>>> Besides that, I found that it is very temporal whether mirroring is
>>> possible or not:
>>> - today = validation error in the gmf.examples area
>>> - Sat a week ago = validation error in the xtext area
>>> - Tue a week ago = mirroring possible
>>> - Sat 2 weeks ago = validation error in the modisco area
>>> ...
>>>
>>> What's up?
>>>
>>>
>>> Michael
>>
>
|
|
|
| Re: B3 Aggregator + Helios Site [message #608273 is a reply to message #535469] |
Sun, 23 May 2010 21:46 |
|
Well, one solution is to use the p2 mirrorApplication, but that's not my
favourite solution as this seems to be more or less a wget for repos.
A cool feature for the b3 aggregator would be to mirror only the newest
artifacts without having to specify version constraints for each IU
(similar to the p2 install dialog where one can hide old versions).
Another help would be regex exclusions for IUs (e.g. exclude *javahl*
instead of 12 IUs containing javahl).
Michael
On 05/23/2010 11:04 PM, Henrik Lindberg wrote:
> So, how should someone that wants to use Helios repo in their own
> aggregation work around this issue?
>
> - henrik
>
> On 5/23/10 10:23 PM, Thomas Hallgren wrote:
>> I think the main reason is that what you find at releases/helios is an
>> aggregate that contains older versions along with the new ones. The b3
>> aggregator creates a repository that is validated. The composite
>> however, is several such repositories. Put together, they no longer
>> represent a 100% coherent repository.
>>
>> - thomas
>>
>> On 05/23/2010 08:00 PM, Henrik Lindberg wrote:
>>> A very possible reason is that there are actual errors in the input.
>>>
>>> Helios is a moving target, and as Dave Williams can testify there is
>>> almost always some contributor that has some problem/conflict.
>>>
>>> These issues are gradually solved until a release ready Helios site is
>>> produced.
>>>
>>> I don't know if good helios repos are kept somewhere.
>>>
>>> - henrik
>>>
>>> On 5/23/10 7:24 PM, Michael Pellaton wrote:
>>>> Hello
>>>>
>>>> Obviously, B3 aggregator is used to assemble the Helios milestone site.
>>>>
>>>> I try to mirror the entire Helios site using B3 aggregator and I often
>>>> run into problems during the validation phase.
>>>>
>>>> Why can't I mirror the Helios site using the B3 aggregator but the
>>>> entire thing was created using the same program running the same
>>>> validations? How can the site be assembled successfully if there
>>>> are invalid constraints preventing the mirroring?
>>>>
>>>> Besides that, I found that it is very temporal whether mirroring is
>>>> possible or not:
>>>> - today = validation error in the gmf.examples area
>>>> - Sat a week ago = validation error in the xtext area
>>>> - Tue a week ago = mirroring possible
>>>> - Sat 2 weeks ago = validation error in the modisco area
>>>> ...
>>>>
>>>> What's up?
>>>>
>>>>
>>>> Michael
>>>
>>
>
|
|
|
| Re: B3 Aggregator + Helios Site [message #608274 is a reply to message #535470] |
Mon, 24 May 2010 00:56 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Using filters is something that has been discussed - esp. "include only
latest". Not sure if an issue was logged for that...
- henrik
On 5/23/10 11:46 PM, Michael Pellaton wrote:
> Well, one solution is to use the p2 mirrorApplication, but that's not my
> favourite solution as this seems to be more or less a wget for repos.
>
> A cool feature for the b3 aggregator would be to mirror only the newest
> artifacts without having to specify version constraints for each IU
> (similar to the p2 install dialog where one can hide old versions).
>
> Another help would be regex exclusions for IUs (e.g. exclude *javahl*
> instead of 12 IUs containing javahl).
>
> Michael
>
> On 05/23/2010 11:04 PM, Henrik Lindberg wrote:
>> So, how should someone that wants to use Helios repo in their own
>> aggregation work around this issue?
>>
>> - henrik
>>
>> On 5/23/10 10:23 PM, Thomas Hallgren wrote:
>>> I think the main reason is that what you find at releases/helios is an
>>> aggregate that contains older versions along with the new ones. The b3
>>> aggregator creates a repository that is validated. The composite
>>> however, is several such repositories. Put together, they no longer
>>> represent a 100% coherent repository.
>>>
>>> - thomas
>>>
>>> On 05/23/2010 08:00 PM, Henrik Lindberg wrote:
>>>> A very possible reason is that there are actual errors in the input.
>>>>
>>>> Helios is a moving target, and as Dave Williams can testify there is
>>>> almost always some contributor that has some problem/conflict.
>>>>
>>>> These issues are gradually solved until a release ready Helios site is
>>>> produced.
>>>>
>>>> I don't know if good helios repos are kept somewhere.
>>>>
>>>> - henrik
>>>>
>>>> On 5/23/10 7:24 PM, Michael Pellaton wrote:
>>>>> Hello
>>>>>
>>>>> Obviously, B3 aggregator is used to assemble the Helios milestone site.
>>>>>
>>>>> I try to mirror the entire Helios site using B3 aggregator and I often
>>>>> run into problems during the validation phase.
>>>>>
>>>>> Why can't I mirror the Helios site using the B3 aggregator but the
>>>>> entire thing was created using the same program running the same
>>>>> validations? How can the site be assembled successfully if there
>>>>> are invalid constraints preventing the mirroring?
>>>>>
>>>>> Besides that, I found that it is very temporal whether mirroring is
>>>>> possible or not:
>>>>> - today = validation error in the gmf.examples area
>>>>> - Sat a week ago = validation error in the xtext area
>>>>> - Tue a week ago = mirroring possible
>>>>> - Sat 2 weeks ago = validation error in the modisco area
>>>>> ...
>>>>>
>>>>> What's up?
>>>>>
>>>>>
>>>>> Michael
>>>>
>>>
>>
|
|
|
| Re: B3 Aggregator + Helios Site [message #608275 is a reply to message #535470] |
Mon, 24 May 2010 03:28 |
|
On 05/23/2010 11:46 PM, Michael Pellaton wrote:
> A cool feature for the b3 aggregator would be to mirror only the newest
> artifacts without having to specify version constraints for each IU
> (similar to the p2 install dialog where one can hide old versions).
>
It already does this. I haven't seen the errors but my guess is that they relate to features that has been removed in
newer versions.
You can always try aggregating the latest contribution to the composite, i.e.
http://download.eclipse.org/releases/helios/201005210900
- thomas
|
|
|
| Re: B3 Aggregator + Helios Site [message #608277 is a reply to message #535489] |
Mon, 24 May 2010 08:30 |
|
> You can always try aggregating the latest contribution to the composite,
> i.e.
> http://download.eclipse.org/releases/helios/201005210900
When doing that, I get
java.lang.ClassCastException:
org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
org.eclipse.core.runtime.CoreException: java.lang.ClassCastException:
org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
at org.eclipse.b3.util.ExceptionUtils.fromMessage(ExceptionUtil s.java:53)
at org.eclipse.b3.util.ExceptionUtils.wrap(ExceptionUtils.java: 120)
at
org.eclipse.b3.aggregator.engine.RepositoryVerifier.run(Repo sitoryVerifier.java:271)
at
org.eclipse.b3.aggregator.engine.Builder.runRepositoryVerifi er(Builder.java:1109)
at org.eclipse.b3.aggregator.engine.Builder.run(Builder.java:62 1)
at
org.eclipse.b3.aggregator.presentation.AggregatorActionBarCo ntributor$BuildRepoAction$1.run(AggregatorActionBarContribut or.java:267)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.ClassCastException:
org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
at
org.eclipse.b3.aggregator.engine.RepositoryVerifier.run(Repo sitoryVerifier.java:214)
... 4 more
I am using Eclipse SDK 3.6.RC2 + b3 aggregator 0.1.0.r01001
Michael
|
|
|
| Re: B3 Aggregator + Helios Site [message #608278 is a reply to message #535516] |
Mon, 24 May 2010 12:15 |
|
That sounds like a bug. Can you please try with the latest version
(unless that's what you have already) and if this problem is still
present, enter a bugzilla to Modeling/EMFT.b3/aggregator?
Thanks,
Thomas Hallgren
On 05/24/2010 10:30 AM, Michael Pellaton wrote:
>> You can always try aggregating the latest contribution to the composite,
>> i.e.
>> http://download.eclipse.org/releases/helios/201005210900
> When doing that, I get
>
> java.lang.ClassCastException:
> org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
> to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
> org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
> to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
>
> org.eclipse.core.runtime.CoreException: java.lang.ClassCastException:
> org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
> to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
> at org.eclipse.b3.util.ExceptionUtils.fromMessage(ExceptionUtil s.java:53)
> at org.eclipse.b3.util.ExceptionUtils.wrap(ExceptionUtils.java: 120)
> at
> org.eclipse.b3.aggregator.engine.RepositoryVerifier.run(Repo sitoryVerifier.java:271)
>
> at
> org.eclipse.b3.aggregator.engine.Builder.runRepositoryVerifi er(Builder.java:1109)
>
> at org.eclipse.b3.aggregator.engine.Builder.run(Builder.java:62 1)
> at
> org.eclipse.b3.aggregator.presentation.AggregatorActionBarCo ntributor$BuildRepoAction$1.run(AggregatorActionBarContribut or.java:267)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.ClassCastException:
> org.eclipse.equinox.internal.p2.metadata.InstallableUnit cannot be cast
> to org.eclipse.equinox.p2.metadata.IInstallableUnitPatch
> at
> org.eclipse.b3.aggregator.engine.RepositoryVerifier.run(Repo sitoryVerifier.java:214)
>
> ... 4 more
>
>
>
> I am using Eclipse SDK 3.6.RC2 + b3 aggregator 0.1.0.r01001
>
> Michael
|
|
| |
| Re: B3 Aggregator + Helios Site [message #608565 is a reply to message #535450] |
Wed, 23 June 2010 13:57 |
Lars Fischer
Messages: 105
Registered: July 2009 |
Senior Member |
|
|
Hello,
I tried to mirror the final helios p2 site with the b3 aggregator.
I created a .b3aggr file with one contribution, mapping the helios url:
http://download.eclipse.org/releases/helios/
Running this, I get this error:
Loading all repositories
Starting generation of composite repository
Adding child meta-data repository
http://download.eclipse.org/releases/helios
Done. Took 0 seconds
Starting generation of verification feature
Done. Took 0 seconds
Starting generation of categories
Done. Took 0 seconds
Starting planner verification
Verifying config win32,win32,x86...
Verifying config win32,win32,x86_64...
Verifying config linux,gtk,x86...
Software being installed: all.contributed.content.feature.group 1.0.0
Missing requirement for filter properties ~= $0:
org.eclipse.ecf.core.featurepatch.feature.group 3.3.0.v20100615-1452
requires 'org.eclipse.ecf.core.featurepatch.feature.jar
[3.3.0.v20100615-1452]' but it could not be found
Cannot satisfy dependency: all.contributed.content.feature.group 1.0.0
depends on: org.eclipse.ecf.core.featurepatch.feature.group 0.0.0
Where is my mistake?
Regards,
Lars
|
|
|
| Re: B3 Aggregator + Helios Site [message #608567 is a reply to message #542006] |
Wed, 23 June 2010 16:30 |
Filip Hrbek
Messages: 233
Registered: July 2009 |
Senior Member |
|
|
I created a bugzilla issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=317727
Filip
Lars Fischer wrote:
> Hello,
>
> I tried to mirror the final helios p2 site with the b3 aggregator.
>
> I created a .b3aggr file with one contribution, mapping the helios url:
> http://download.eclipse.org/releases/helios/
>
> Running this, I get this error:
>
> Loading all repositories
> Starting generation of composite repository
> Adding child meta-data repository
> http://download.eclipse.org/releases/helios
> Done. Took 0 seconds
> Starting generation of verification feature
> Done. Took 0 seconds
> Starting generation of categories
> Done. Took 0 seconds
> Starting planner verification
> Verifying config win32,win32,x86...
> Verifying config win32,win32,x86_64...
> Verifying config linux,gtk,x86...
> Software being installed: all.contributed.content.feature.group 1.0.0
> Missing requirement for filter properties ~= $0:
> org.eclipse.ecf.core.featurepatch.feature.group 3.3.0.v20100615-1452
> requires 'org.eclipse.ecf.core.featurepatch.feature.jar
> [3.3.0.v20100615-1452]' but it could not be found
> Cannot satisfy dependency: all.contributed.content.feature.group 1.0.0
> depends on: org.eclipse.ecf.core.featurepatch.feature.group 0.0.0
>
>
> Where is my mistake?
>
>
> Regards,
> Lars
>
|
|
|
Goto Forum:
Current Time: Fri Apr 19 14:45:46 GMT 2024
Powered by FUDForum. Page generated in 0.02511 seconds |
] 
Search
Help
Register
Login
Home
