These are chat archives for etorreborre/specs2

19th
Apr 2018
Marko Dimjašević
@mdimjasevic
Apr 19 2018 07:18
That's right. I've kindly ask for a release that includes this feature from its master branch for quite a few times, but it hasn't happened yet
so I just created a company-internal fork of ScalaCheck so that I can make an internal release
Then I'll proceed with extending specs2 per your guidelines here in the channel from Jan 22: https://gitter.im/etorreborre/specs2?at=5a65c9ad98927d57451e6551
@etorreborre I'll ping you if I'll have any questions and make a pull request. Then hopefully soon after that you can make a specs2 release that includes this feature.
Eric Torreborre
@etorreborre
Apr 19 2018 07:20
seems like a plan!
Marko Dimjašević
@mdimjasevic
Apr 19 2018 10:11
Can specs2 be used with ScalaCheck without specifying "org.specs2" %% "specs2-scalacheck" in SBT?
Marko Dimjašević
@mdimjasevic
Apr 19 2018 10:17
@etorreborre : ^^
Eric Torreborre
@etorreborre
Apr 19 2018 10:21
I don’t see how you would get the ScalaCheck trait to be mixed-in your specification otherwise
Marko Dimjašević
@mdimjasevic
Apr 19 2018 10:34
@etorreborre: So how would I combine specs2 with my own fork of ScalaCheck?
Eric Torreborre
@etorreborre
Apr 19 2018 11:05
You’re not going to like the answer. You need a fork of specs2 as well (at least of specs2-scalacheck)
Maybe we can create a specs2-scalacheck-seed subproject depending on your fork?
Marko Dimjašević
@mdimjasevic
Apr 19 2018 11:08
Hm
What would that subproject be for?
Oh, so the subproject would be pretty much the same as specs2-scalacheck except that I could plug in my fork of ScalaCheck?
Eric Torreborre
@etorreborre
Apr 19 2018 11:10
yes I think that could work
Marko Dimjašević
@mdimjasevic
Apr 19 2018 11:10
Ok, so I'd have to have a publicly accessible fork of ScalaCheck
Eric Torreborre
@etorreborre
Apr 19 2018 11:10
really not ideal because we need to maintain duplicated code
yes that’s be better for the people wanting to use that module as well
Marko Dimjašević
@mdimjasevic
Apr 19 2018 11:11
I know, but I've been asking for a release of ScalaCheck for half a year now and I'm not the only one
Eric Torreborre
@etorreborre
Apr 19 2018 11:11
but frankly this is all a bit ridiculous
Marko Dimjašević
@mdimjasevic
Apr 19 2018 11:11
agreed
a question or two about the Maven infrastructure... do I need an account to push to Maven Central?
Eric Torreborre
@etorreborre
Apr 19 2018 11:12
I’m using sonatype to publish jars, then they do the sync
Marko Dimjašević
@mdimjasevic
Apr 19 2018 11:12
I think ScalaCheck is too. Do I need to set up an account or something?
Eric Torreborre
@etorreborre
Apr 19 2018 11:13
There’s a doc somewhere on the Sonatype website explaining how to do it. I forgot but I think it starts with creating a JIRA ticket
Let’s try to ping Ricky one more time: rickynils/scalacheck#374
Marko Dimjašević
@mdimjasevic
Apr 19 2018 11:30
sure. I appreciate all the effort that ScalaCheck contributors have done (including the main author), but it's ridiculous not to reply for half a year and at the same time not give permissions to anyone else to make a release that is badly needed.
Hopefully my fork is just a temporary thing until the upstream ScalaCheck makes a new release.