-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the dependency on specs2 more explicit throughout #5
Labels
Comments
Closed
franckrasolo
added a commit
that referenced
this issue
May 5, 2014
franckrasolo
added a commit
that referenced
this issue
May 5, 2014
franckrasolo
added a commit
that referenced
this issue
May 5, 2014
franckrasolo
added a commit
that referenced
this issue
May 5, 2014
franckrasolo
added a commit
that referenced
this issue
May 5, 2014
franckrasolo
added a commit
that referenced
this issue
May 16, 2014
franckrasolo
added a commit
that referenced
this issue
May 31, 2014
franckrasolo
added a commit
that referenced
this issue
Jun 1, 2014
franckrasolo
added a commit
that referenced
this issue
Jun 1, 2014
franckrasolo
added a commit
that referenced
this issue
Jun 3, 2014
franckrasolo
added a commit
that referenced
this issue
Jun 3, 2014
franckrasolo
added a commit
that referenced
this issue
Jun 6, 2014
franckrasolo
added a commit
that referenced
this issue
Jun 11, 2014
…n their respective target directories
franckrasolo
added a commit
that referenced
this issue
Jun 11, 2014
… their respective target directories
franckrasolo
added a commit
that referenced
this issue
Jun 11, 2014
to their respective target directories
franckrasolo
added a commit
that referenced
this issue
Jun 11, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The project's README file and the base package name already clearly state the dependency on specs2. However, given that we agree that it would be useful to the wider community to be able to use Clairvoyance with ScalaTest, I suggest doing the following:
1. rename the artifact from(related to #4)clairvoyance
toclairvoyance-specs2
2. renameorg.specs2.clairvoyance
toclairvoyance
3. abstract awayclairvoyance.export
4. push down specs2 implementations toclairvoyance.specs2
andclairvoyance.specs2.export
The text was updated successfully, but these errors were encountered: