Move tests into their own project

[mdedetrich]

This is to prevent the test dependencies showing up in the pox.xml, helpful for @fommil in spray-json. See spray/spray-json#232 (comment)

[fommil]

It's not for me. It's for the entire community. You'll understand when 2.13.0 is released.

Releasing untested software is not the solution here. You need to rewrite your tests to be zero dependency other than scala-lang.

[mdedetrich]

Releasing untested software is not the solution here.

Thats not the idea, the idea is to remove the tests from the pom.xml (travis will be changed so it will always run the tests from the subproject)

You'll understand when 2.13.0 is released.

Afaik, the major testing frameworks were doing their releases against a prereleased Scala well before the actual release of a Scala major was done for this exact reason. I know that ScalaTest did this.

I mean what is the problem here for you specifically? If its dependencies in the pom.xml, I can still remove it from the POM but enforce tests via sbt. Another option is to use a direct git dependency for tests

[mdedetrich]

I am going to close this because @fommil doesn't seem to be entirely consistent with the problem and this appears to be a non issue in reality

• Spray-json also has these same test dependencies (see Integrate with, the one and only, ScalaJSON spray/spray-json#232 (comment))
• Regarding internal fork of spray-json and spray-json-shapeless ensime/ensime-server#1821 and reduce scala dependencies ensime/ensime-server#1398, some typelevel projects also contain the same test dependencies as ScalaJSON ast
• We are talking about test dependencies here?

[fommil]

I don't want to be involved with this project, please leave me out of it.

[mdedetrich]

I don't want to be involved with this project, please leave me out of it.

Thats why this issue is closed as a non issue 😉