Dependencies declared with scope=test in the original project
(google-cloud-storage) won't come in transitively, you'd have to copy/paste
them.
Ideally, if that use case were to be officially supported, the project
would have to publish the tests as a normal JAR at different coordinates,
so it wou
I'm attempting to run the tests in a test jar rather than from source,
for reasons. That is, I set up the pom.xml like so to run the tests
that are bundled in
com.google.cloud:google-cloud-storage:test-jar:tests
org.apache.maven.plugins
maven-surefire-plugin
> Hi Dave.
>
> I recommend to start with a simple stand-alone project in order to
> find out how Maven Shade works. It can be quite tricks for beginners
> otherwise. Create a
Typo: I mean "tricky", of course.
> POM, add a dependency - any dependency, some open source library maybe
> - and then t
Hi Dave.
I recommend to start with a simple stand-alone project in order to find out how
Maven Shade works. It can be quite tricks for beginners otherwise. Create a
POM, add a dependency - any dependency, some open source library maybe - and
then try shading and relocating it with Maven Shade.
I have a single module Maven build where one of the dependences has well
over 200 transitive dependencies. These transitive dependencies are
incompatible with the rest of my application.
I would like to use the maven-shade-plugin to create a shaded jar uber jar
that contains all of these dependen
Milestone means "work in progress" and if you are continuously breaking
backwards compatibility, you can do it in multiple milestones. It does not
make sense to release multiple release versions because it's risky for
users. This email has convinced me to publish a pull request with changes
mandato
