This repository has been archived by the owner on Apr 27, 2022. It is now read-only.
[WIP] split the Maven module into two new ones #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e plugin and running the tests and one that doesn't)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should address issue #31
I haven't found a way to release the jar with all the deps and the slim one while having only one
pom.xml. There is no configuration for the maven-release-plugin to use ownartifactIdif there is easier way to do this, I am happy to change this. Now there are two new maven modules (w/ different artifactId) that take the same code and one assembles the jar with all the deps (spark-streaming-amqp_2.11-fatjar) and the other one is supposed to be the slim one (spark-streaming-amqp_2.11).todo: run the tests only once (now they are not run at all)