-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Streamlining iplab reviews for BND-wrapped libraries #43
Comments
|
The generator could produce something like this which is effective just the mapping from the OSGi name/version of the Maven coordinates, in json format:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the IP review infrastructure using dash-license for the content generated from
https://github.com/eclipse-orbit/orbit-simrel/blob/main/maven-bnd/tp/MavenBND.target
results duplicate iplab issues that result in approval delays and extra work for the IP staff. It also adversely impacts downstream consumers of Orbit. I'm not sure how best to improve the situation.
In an effort to gather information that might be helpful, I've investigated generating a report that provides information about the mapping between the maven coordinate of each artifact and the osgi bundle symbolic name and version produced for that artifact. In addition, I've collected the associating iplab issue(s) for each artifact.
I will copy and paste a prototype of such an automatically generated report in a separate comment below, which I will update based on feedback
I've create a corresponding iplab issue:
https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/16675
The text was updated successfully, but these errors were encountered: