| Re: [orbit-dev] Adding an existing bundle from Maven to Orbit |
Hi Dirk,
One reason for the Mapping in the past was to have correct metadata for strings visible in the Eclipse IDE. For example, we used to set bundle vendor to "Eclipse Orbit" of all bundles from Orbit. This helps developers to identify where a bundle is coming from.
Having said that, I'm not sure that we still need this requirement. Is someone working on the Windows issue? Is it related to EBR?
Does pom dependencies also work when adding the bundle to features? What if we create a special feature for "unwrapped" (direct) dependencies fetched from Maven?
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/
> On Sep 20, 2019, at 11:48, Dirk Fauth <dirk.fauth@xxxxxxxxxxxxxx> wrote:
>
> Hi,
>
> while playing around with adding GlazedLists 1.11.0 to Orbit I realized the fact that the GlazedLists jar is already a valid bundle with OSGi metadata generated by the bnd plugin. So the wrapping that happens by EBR is actually not necessary.
>
> I remembered that in the past I was able to create an update site with bundles from Maven WITHOUT additional wrapping. I have attached a small example to show this. Basically it uses pomDependencies==consider and the bundle is added to the category.xml manually.
>
> Would that be a possible solution? Actually I can't test an integration as I would need to setup a Linux environment, as the build fails on Windows. But maybe someone could support here?
>
> Greez,
> Dirk
> <consider_test.zip>_______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/orbit-dev