Redistributing org.gradle.toolingapi about buildship HOT 1 OPEN

Hi Ed! Sorry for the late reply, I was offline in the past few weeks. The Tooling API jar is indeed not published to maven central. That the jar we publish to repo.gradle.org does not have the OSGi metadata, that's why we repackage and publish it in the Buildship build. There's quite a bit of code for that in the repository, and because we only use it for Buildship, it was natural to keep everything in the same repository.

Back then we considered publishing the tapi jar to orbit, but we concluded that without consumers outside of Buildship, it does not make sense to maintain a shared bundle. If there's a potential consumer, however, we should change that and publish it. For that the easies solution, as you said, is to use what we have. Generating the OSGi-ified jar is rather simple:

• update the tapi version in gradle.properties
• run the createP2Repository task: ./gradlew :org.gradle.toolingapi:createP2Repository

from buildship.