Conversation
Member
|
Oh, and I think you know the Ivy mechanisms for this. What we need to do is get Ivy aware of the "testjar" artifact classifier. If there's not already an ivy issue open, please do so. We have a branch of Ivy we can try to add that support in. |
Contributor
Author
|
Hey Josh, That was a lot of helpful comments, but I have failed to grasp it all or somehow get this to work. I have tried working with "test->test" or classifier as configuration. But somehow it does not work. |
Contributor
Author
|
Closing this in favor of #14. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
So I am trying to make
someproject.dependsOn(streaming % "compile->compile;test->test")work somehow.In maven this happens by specifying that we want to publish test jar for a particular artifact and then later require
<type>astest-jarwhere it is actually needed. In SBT this is opposite, in the sense the project itself is not marked to publish test-jars but someproject may dependsOn its test jar. So this information is only required at only one place i.e where it is actually required.