zcaudate
commented
9 years ago Hey Rick,
That's a good idea. I had wanted to do something like that but it was a pain trying to figure the design of configuration options.
The first step is to make an example project, along with options that gives us what we want. You can check out some of the previous test cases in the examples directory. I'll give you access to the repo so you can just push directly.
Chris.
On 7 Feb 2015, at 23:38, Rick Moynihan notifications@github.com wrote:
I think the feature that I'd actually love, is to be able to provide a list of namespaces as configuration and have repack create jars for each of those, pulling in transitive namespace dependencies and packaging them in jars.
The reason is for me, looking at namespace definitions "level" doesn't always align with a useful package. I'd essentially like more control of the curation aspect.
Obviously you'd need some way for repack to either identify common overlapping namespaces and put them in a single common package; or have it throw an error to the packager telling them that have to define a comon package.
— Reply to this email directly or view it on GitHub.
I think the feature that I'd actually love, is to be able to provide a list of namespaces as configuration and have repack create jars for each of those, pulling in transitive namespace dependencies and packaging them in jars.
The reason is for me, looking at namespace definitions "level" doesn't always align with a useful package. I'd essentially like more control of the curation aspect.
Obviously you'd need some way for repack to either identify common overlapping namespaces and put them in a single common package; or have it throw an error to the packager telling them that have to define a comon package.