Re: Extracting classes from a separate project?

Great question! I see a couple of approaches: 1) Technical solution: I think you are on the right track to use the maven-shade-plugin. But you shouldn't need the maven-dependency-plugin. The shade plugin is pretty powerful. Why not just make your single-module library artifact an "uber-JAR"

Re: Extracting classes from a separate project?

'Lo, On 2015-12-01T10:45:16 -0600 Curtis Rueden wrote: > Great question! > > I see a couple of approaches: > > 1) Technical solution: I think you are on the right track to use the > maven-shade-plugin. But you shouldn't need the maven-dependency-plugin. The > shade plugin

Re: Extracting classes from a separate project?

On 2015-12-01T17:56:15 + wrote: > > On 2015-12-01T10:45:16 -0600 > Curtis Rueden wrote: > > Why not just make your single-module library artifact an "uber-JAR" > > consisting > > only of its own sources plus the relocated+minimized

Extracting classes from a separate project?

Hello. I'm intending to use some classes from the fastutil package[0]. Due to the size of the artifact(s), it's assumed that anyone using the package will use ProGuard on their application to remove unneeded classes. However: 1. I'm writing a library. 2. I'm using the fastutil classes in a way