the use of maven shade plugin

[jnorthrup]

I noticed a couple of things in the build scrolling by related to maven shade plugin.

I have found a somewhat cheaper and cleaner workaround to shade which removes all the manifest collisions I have ever encountered to date and is far less likely to provoke the legal team in times of open-source license reviews:

-- using the deps plugin to dump a libs dir in target/

this is cheap and lives in inner target to accompany a script classpath of

-cp "$PWD/target/classes:$PWD/target/lib/*" pkg.random.ClassWithMain

or in the parent pom with undefined specificity:

<build>
        <plugins>
            <plugin>
                <artifactId>maven-dependency-plugin</artifactId>
                <executions>
                    <execution>
                        <phase>install</phase>
                        <goals>
                            <goal>copy-dependencies</goal>
                        </goals>
                        <configuration>
                            <outputDirectory>${project.build.directory}/lib</outputDirectory>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>

the cp using $PWD/target/classes can also be $PWD/target/* to use the maven final jar depending on if you want to edit live code and run compile, or package respectively during development. both in the same classpath is not advised.