"java package bloat" - dealing with constellations of packages #21
Description
Now that the java build process is moderately standardized, we still have the issue of always working with constellations of packages. For example, a normal java app is going to have a code package, a test package, a linter package (maybe?), and a release package. That sucks. How can we define standard sets of packages? Will it be like 3pi shitting packages all over but we don't care because at least we didn't have to generate them by hand? Or something else?