I just came across the fact that a Show[Throwable] exists.

1. It is not wired up into import Scalaz._, one needs to import scalaz.std.java.throwable._
2. It discards the stack trace entirely.

What's going on with this? :D
Is it OK if I fix both of these (for 7.2 and 7.3)?

Per the BufferedInputStream documentation, the skip(n) method corresponds to the general contract in InputStream. Which is:

"If n is negative, the skip method for class InputStream always returns 0, and no bytes are skipped. Subclasses may handle the negative value differently. "

From this I'd expect scala-native's BufferedInputStream.skip to return 0. Instead an `IllegalArgumentEx

I didn’t see any documentation on the publish command other than the help.

I have questions such as:

In sonatype there are a number of checks that must be passed by the repo (having java docs, sources, signatures, and probably more). Is there an example that shows the full process of doing a publish to sonatype?

The original CrossProject in SJS has quite extensive documentation, notably about some common pitfalls. It should be carried over (maybe to README.md).

This issue should remain open as a reminder to periodically review commits and port the issue across. If you find a new PR/commit, please open a new issue to handle that commit.

• lightbend/config#619 Allow application.conf to override variables in reference.conf

Consider the build.sbt from scalajs-react-template. For the most part, it's just dependencies, and translating them to Maven using scalor-maven-plugin is straightforward.

There are basically at least three other concerns:

1. Settings such as packageJSDependencies. jsDependencies, etc.
2. Scoping those `Setting

I don't see a mention of this in the documentation.

The logger methods don't take their msg param by-name, but I guess the macro implementations may be providing that "laziness" to the msg-construction.

If I have a complicated interpolated string, I don't want to create it unless I am ac

I'm not sure if the warning is intended as a test, however, in that case we might want to have a way to capture and ensure that the warning is reported.

[info] BindgenSpec:
[info] Bindgen
[info] - should exist
[info] - should generate bindings for native.h
[info] - should generate bindings for PrivateMembers.h
[info] - should generate bindings for Enum.h
[info] - should generate bind