| Re: [orbit-dev] Orbit artefacts in Maven repository |
This has come up in the past and it was determined it would be out of
scope for Orbit.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=484631
(particularly comment 8)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=484633
New Orbit bundles (built with EBR) can all be mapped to the original
maven coordinates that were used to generate them. In some cases the
artifacts can't be found on Maven Central, so we host the content
ourselves at 'orbit-approved-artifacts', as those bugs describe.
As has been mentioned, it's possible for the final generated bundle to
differ from the original artifact in more than just the manifest data.
Certain classes might need to be excluded for legal reasons, and in
some cases, additional modifications may be needed to resolve
vulnerabilities/bugs where updating is not feasible.
Hope this at least shows some of the challenges with doing this.
Cheers,
--
Roland Grunberg
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/orbit-dev