Open
Conversation
vic
force-pushed
the
scalajs
branch
2 times, most recently
from
4c9bce9 to
217affb
Compare
|
Also interested, can this be merged? |
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
2 participants
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.
Hi, @ngocdaothanh
First of all, thanks for writing scaposer! We are trying to use it from an scalajs front-end application.
This pull request adds cross-compilations to latest scalajs stable release. Also upgraded the
specs2-coredependency to match the latest published for scalajs compatibility.Removed the
fork in Test := truecode frombuild.sbtsince the issue scala/scala-parser-combinators#197 has already been solved in sbt1.3.x.Added a
jitpack.ymlin order to be able to fetch artifacts for non-release versions (like this patch) by using jitpack.io.