Re: [orbit-dev] Adding an existing bundle from Maven to Orbit

[Dirk Fauth <dirk.fauth@xxxxxxxxxxxxxx>]

OK, I have to admit that I was not aware of the fact that the source bundle also has to be an OSGi bundle.

I think that sources are important. Especially because companies nowadays need to perform OSS scans. And of course for debugging purposes.

As all the other resources are also wrapped, I suppose I should not push the direction any further and simply accept that the OSGi bundle gets wrapped to be consumable via Orbit.

Or would it be possible to only wrap the source bundle?

On Fri, Sep 20, 2019 at 8:07 PM Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:

> On Sep 20, 2019, at 16:48, Roland Grunberg <rgrunber@xxxxxxxxxx> wrote:
>
> On Fri, Sep 20, 2019 at 8:36 AM Dirk Fauth <dirk.fauth@xxxxxxxxxxxxxx> wrote:
>> I think creating such a feature would work. I could give it a try with the example I provided.
>
> You're right pomDependencies=consider could work and could
> get resolved by a separate feature. There's one issue though, in
> the case of glazedlists. com.glazedlists:glazedlists:1.11.0:sources
> is not an OSGi bundle, so source feature generation fails.


Bummer. I don't expect any of the ready-to-use bundles to have a source bundle for Eclipse. Thus, this feature either needs to disable source generation (we won't ship sources for it) or we need to continue wrapping the bundles for the purpose of having source.

-Gunnar


--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/


_______________________________________________
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