sbt-github-packages | A simple sbt plugin for publishing to GitHub Packages, in the style of sbt-sonatype and sbt-bintray | Build Tool library

Executive summary: I'd like to, if possible, just upload a directory full of files to a "GitHub Package". Not a GitHub "repository", but a "Github Package", which are described here. Unfortunately, the documentation doesn't tell you how to do such a thing. It only tells you how to upload build artifacts using build tools for JavaScript, Ruby, Java, and .NET.

Why do I want to do this? I answer this immediately below. Though if there is also an easy solution using Maven, then Maven will also work for me:

We're hoping to migrate from a locally-hosted Nexus artifact repository to GitHub Packages as a way of making our build artifacts (e.g., jar files) available to everyone in our development team.

The programming language we're using is Scala, which is a JVM-targeted language, so it's designed to largely interoperate with the Java ecosystem. For managing builds, however, we use sbt, not Maven. Sbt is the standard Scala build tool.

There is a plugin for sbt (called sbt-github-packages), which actually works great. It allows us to easily publish our Scala jar files, etc., to GitHub just by typing "sbt publish".

The problem that we have yet to solve, however, is uploading to a GitHub Package third-party artifacts, such as Oracle's jdbc drivers. This is not a problem for most third-party artifacts, since most of them are stored in publicly available Maven or Ivy artifact repositories, and sbt will just automatically fetch them as needed.

Unfortunately, Oracle doesn't provide their jdbc drivers in such a standard way. There are also other artifacts we need to use that we don't author and which are not located in public artifact repositories. We currently solve this problem by uploading them into our locally-hosted Nexus artifact repository.

The instructions on GitHub for publishing artifacts to GitHub Packages say only to cd into your Java source code Git repo and type "mvn deploy". (You have to add some config stuff to the pom file first, but that's easy enough.) But these instructions are intended for compiling Java source code and then publishing the compiled artifacts into the GitHub Package. They are not complete instructions that tell you how to deal with the case where you don't have source code, but instead have only prebuilt artifacts.

I'm sure that if I understood Maven well, I could probably figure out how to make this work, but I know very, very little about Maven. As I mentioned above, we use sbt instead.

I did get something to work, but it's not quite right. I made a directory with all of Oracle's ojdbc7 artifacts. I made a symlink from ojdbc7-12.1.0.2.pom to pom.xml and then I ran "mvn deploy". This did upload ojdbc7-12.1.0.2.jar and ojdbc7-12.1.0.2.pom to the GitHub Package, but other artifacts were not uploaded. For instance, this did not upload ojdbc7-12.1.0.2-javadoc.jar.

Also, if there were a source-code jar in this directory, I'm sure that it also wouldn't have been uploaded.

If anyone knows what I need to do to publish to the GitHub Package all of the artifacts in my ojdbc7 directory, I will be very thankful.