As per #459 (comment).
Currently, the build system generates a fat jar and then plops it in the root of the repo, which is odd (manual steps take over at that point to publish that jar somewhere else). If generating a fat jar must be done, might as well have the same hosting for the normal jar and the fat jar. Users without build systems (😱 ) can still download the fat jar from the distribution site if they need to.
Rough implementation plan (this is just one way, there are other ways to do it):
- Switch to hosting on Bintray because it's so much simpler to use as an author than Sonatype's OSS
- Upload the normal jar, pom, etc to a Bintray package
- Generate a different pom for the fat jar (perhaps by making the fat jar a submodule?) that has no dependencies
- Upload the fat jar and its dependency-free pom to a different Bintray package
As per #459 (comment).
Currently, the build system generates a fat jar and then plops it in the root of the repo, which is odd (manual steps take over at that point to publish that jar somewhere else). If generating a fat jar must be done, might as well have the same hosting for the normal jar and the fat jar. Users without build systems (😱 ) can still download the fat jar from the distribution site if they need to.
Rough implementation plan (this is just one way, there are other ways to do it):