Re: [ebr-dev] Build fail

[Frank Benoit <fr@xxxxxxxxxxxx>]

Hi Gunnar,

thanks for the reply.

I tried to create a recipe for rxjava. I am not sure if it already exists somewhere, i have not found it.

But there is https://github.com/ReactiveX/RxJava/issues/2598, which makes me wonder if rxjava is bundleable in a clean way.

Nethertheless, it looks good so far.

I choose the plugin name "rxjava.ebr_1.0.14"

Added to 

recipes\unsorted\pom.xml 

releng\p2\aggregationfeature\feature.xml 

If EBR would now implement the last step of automation: a continuous build server.

E.g. as soon as rxjava publishes 1.0.15, an automated re-creation of the ebr is triggered and made visible online. -> perfect

Frank

2015-10-27 16:05 GMT+01:00 Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>:

Hi Frank,

> Am 27.10.2015 um 00:03 schrieb Frank Benoit <fr@xxxxxxxxxxxx>:
> I would have expected a lot more, so i think something went wrong.
> Can you help?

Unfortunately, Tycho is unable to mirror bundles into a p2 repository which have not explicitly been references by their bundle symbolic name. Therefore, every bundle must be added the the aggregation feature.

If you look at the feature, it currently only lists 3 bundles:
https://github.com/eclipse/ebr/blob/master/releng/p2/aggregationfeature/feature.xml

I haven't had a chance yet to add all the missing bundles to the feature. Therefore they are missing in the resulting p2 repository.

FWIW, that's the reason you are seeing the giant p2 mirroring resolution errors logged as warning when building the repo. Because I use queries in the category.xml, Tycho correctly finds the metadata and adds all of them to the categories. However, it then fails to find and mirror the artifacts.

The bug to track is here:
https://bugs.eclipse.org/371983


The following warning can be ignored:
"Unused Export-Package instructions: [*.impl*]"

It's generated by bnd for the bnd file being too broad. Some bundles share a common bnd file. Thus, we do list a few package import/export rules in there. Some do not apply to all of the bundles. Bnd doesn't like that and issues a warning. The resulting bundle MANIFEST.MF is still correct, though.

-Gunnar
_______________________________________________
ebr-dev mailing list
ebr-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ebr-dev