Wayne Beaton

The build does push the bits to our Nexus instance. ```bash curl -L "https://repo.eclipse.org/service/local/artifact/maven/redirect?r=dash-licenses&g=org.eclipse.dash&a=org.eclipse.dash.licenses&v=LATEST" -o license.jar ``` But... we should probably still push it to download.eclipse.org. And it's probably time...

The IContext notion doesn't allow for extensibility. Dependency injection would likely be a better solution that would make it possible to, for example, reuse some of the services in a...

As more projects incorporate this into their builds, we're going to hit the rate limit more frequently. We should probably try to address that. I assume that there's some way...

Thanks for the report. There was a regression in the data (not the tool). I am investigating. I recently tweaked how we sort out the license from Orbit data (which...

Any volunteers? Unfortunately, I've never done any of the above and am starting from zero knowledge.

There is. I guess that I have some homework to do.

I've created a [build](https://ci.eclipse.org/dash/job/dash-license-tool/). I'll try to sort out how to push the results to repo.eclipse.org later this afternoon.

I've [requested](https://bugs.eclipse.org/bugs/show_bug.cgi?id=570377) some space on repo.eclipse.org.

> I guess Fred knows how to configure that That's a pretty good guess. :-)

Deployed. Look [here](https://repo.eclipse.org/index.html#view-repositories;dash-licenses-snapshots~browsestorage~/org/eclipse/dash/license-tool-plugin/0.0.1-SNAPSHOT/license-tool-plugin-0.0.1-20210124.234121-1.jar). The job is currently configured to run manually.