Re: [cross-project-issues-dev] Can Orbit also host "p2-ified" OSGi bundl

[Roland Grunberg <rgrunber@xxxxxxxxxx>]

> Hi all,
> Some OSGi bundles are existing on Maven, great. Tycho is able to consume them
> directly with the "pomDependencies=consider" option, great too.
> However, this pomDependencies=consider doesn't have an equivalent in PDE
> target-platform like p2 has. So it makes that using directly OSGi bundles
> from Maven make it tricky to provide a portable target platform definition
> (.target file).
> Do you think it would make sense for Orbit to also host those external
> bundles, without rebuilding them, and pusblish them as p2 artifacts? I'll
> probably need it soon for GSon 2.5.0.

So you want a p2 repository of artifacts directly from maven. If this is the
case then this seems like a special case of what might already happen with the
new orbit-recipes approach.

With the new orbit-recipes approach, we call ebr-maven-plugin to generate a
manifest for some artifact from maven. I think we do this in all cases, but
if a maven artifact already has its own OSGi metadata, then I don't think we
should be re-generating the metadata unless its clearly wrong.

However, we still need to sign the bundles and add about.html, as well as the
license under about_files/ so they wouldn't be completely untouched, but the
metadata could be left as is.

Another thing that's going to change about this new process is that instead of
grabbing the bundles directly from maven-central, Orbit committers will end up
uploading them to an Eclipse-hosted Maven repository [1]. This also handles cases
for content that isn't in maven central.


Cheers,
-- 
Roland Grunberg

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=484631