Skip to content

What can we do to avoid duplicates for Orbit libraries produced using BND instructions?

I opened this issue in Orbit:

https://github.com/eclipse-orbit/orbit-simrel/issues/43

The current dash-license infrastructure that results in duplicate issues is problematic, causes delays, and creates overhead for everyone involved, i.e., for Orbit, for the consumers of Orbit, and for the IP staff.

Currently the content as reported below are source of confusion and frustration. In each case there is an approved ✔ issue for which there is a duplicate open ❌ issue for the same artifact. I raise this issue as an urgent once now because I need to produce an M2 milestone of Orbit tomorrow for consumption by the Platform's M2 on Wednesday. But the current state is extremely poor. Every project using dash-license that is downstream from Orbit using a nightly builds is already having problems and if I build a milestone that includes the new batik, that problem will grow.

All the information about the duplication is available and I can produce it in any form that is most-easily consumed.

What can I do to help streamline this process?

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent