Details
Description
currently as a project our "convenience binary" for java is the complete set of jars, source jars, test jars, and javadoc jars. that means as a part of RC vetting someone has to check all of those individual files in addition to checking them in the staged nexus repo.
the overwhelming majority of java users will consume our releases via maven central. we should either
- ship nothing for java out of dist.a.o
- ship a tarball that contains the things we currently ship
- ship a tarball that is a laid out like a repository and includes both our artifacts and transitive dependencies
my personal preference is for "ship nothing". The last option would have the most potential use IMHO, since it would allow someone to easily set up a local repository when they need to build against our artifacts.