eclipse
Orbit recipe (EBR) repository does not retain historical data
The Eclipse ESCET automated license check found another regression in accepted licenses. These concern CQs, so I'm not sure why the Dash license check tool suddenly no longer considers them accepted as of today:
-p2/orbit/p2.eclipse-plugin/org.bouncycastle.bcpg/1.65.0.v20200527-1955, Apache-2.0, approved, CQ21975
-p2/orbit/p2.eclipse-plugin/org.bouncycastle.bcprov/1.65.1.v20200529-1514, MIT AND LicenseRef-Public-Domain, approved, CQ21977
+p2/orbit/p2.eclipse-plugin/org.bouncycastle.bcpg/1.65.0.v20200527-1955, unknown, restricted, none
+p2/orbit/p2.eclipse-plugin/org.bouncycastle.bcprov/1.65.1.v20200529-1514, unknown, restricted, none
The back end pulls some data from the Eclipse Orbit orbit-recipes repository. I'll investigate.
In the meantime, I've added a hint to the back end so that this content passes. I'll leave this issue open until after I resolve the back end issue.
It turns out that I misunderstood how the project team managed the Orbit repository.
The Eclipse Dash License Tool connects with the EF server to get license data. The process on the back end gets data from a few different places, e.g., IPzilla and Orbit. There are two different sources for Orbit data: one of them is the orbit-recipes Git repository.
All new information goes into this repository. When a new version of existing content is added, the old data is deleted. We'll have to update the back end to consider history from this repository (one way or another). AFAICT, other than screen scraping the Orbit website, there is no other source of complete (including) historical data. I'll connect with the Eclipse Orbit team to validate my understanding.
@waynebeaton now would be a good time to connect with the Eclipse Orbit team (aka me :-) as in the next coupe of weeks I will be doing some restructuring as announced here: https://www.eclipse.org/lists/cross-project-issues-dev/msg18987.html so it would be a good time (for me!)
