Skip to content

Add support for scala.js runtime #184

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

Merged
merged 1 commit into from
Sep 18, 2016
Merged

Add support for scala.js runtime #184

merged 1 commit into from
Sep 18, 2016

Conversation

lustefaniak
Copy link
Contributor

No description provided.

@gslowikowski
Copy link
Member

Ready to merge?

@lustefaniak
Copy link
Contributor Author

RDY, I tested it locally and scala.js works perfectly.
It fails for me on scripted scoverage/aggregate, but that is also failing on master I think check script misses coverageReport which is not executed after test anymore (and I think in the past it was not needed).

@lustefaniak
Copy link
Contributor Author

Would be great to have scripted tests execute on Travis, I will fix that scripted scoverage/aggregate in next PR.

@gslowikowski
Copy link
Member

OK

@gslowikowski gslowikowski merged commit 04716e2 into scoverage:master Sep 18, 2016
@gslowikowski
Copy link
Member

Some time ago we discussed on Gitter and here about adding sbt-scalajs plugin and using %%% operator.

In Play! Framework Twirl module they went this way: playframework/twirl@104128a (look at build.sbt changes).

@lustefaniak
Copy link
Contributor Author

Can you please explain what you mean? I think I don't undertand, do you mean adding addSbtPlugin in build? That doesn't solve the problem at all, as operator %%% used in that context has completly different meaning than operator used in user project (eg. different versions)

@gslowikowski
Copy link
Member

We talked about using:

        OrgScoverage %%% ScalacRuntimeArtifact % coverageScalacPluginVersion.value,

instead of

        OrgScoverage %% (ScalacRuntimeArtifact + optionalScalaJsSuffix(libraryDependencies.value)) % coverageScalacPluginVersion.value,

here

@lustefaniak
Copy link
Contributor Author

Yes, but that approach would still require pulling in sbt-scalajs plugin. I checked its source code and there is nothing we could reuse, everything depends on hardcoded scala.js binary version.

@lustefaniak
Copy link
Contributor Author

lustefaniak commented Sep 26, 2016

Hi @sjrd can you please confirm if such approach should support future version of scala.js? Or how we could improve that without adding sbt-scalajs to dependencies?

@sjrd
Copy link

sjrd commented Sep 26, 2016

It will work as long as we're in the 0.6.x series. When we switch to the 1.x.y series, the binary _sjs version will be only the major version, so _sjs1 (and not _sjs1.0).

@lustefaniak lustefaniak deleted the add-scala-js-support branch September 27, 2016 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants