JPort License

[summer-alice]

Start off with an easy one :)

What's the license of JPort?

I'm not particularly fussed, but something that doesn't complicate what can be done with the translated code (since the non-translated code will have it's own license) would be ideal.

[jacob-carlborg]

I would like it to be Boost licensed. Unless there are any dependencies that prevent that. Mostly because it's tied to D, where Boost is a very common license. I don't know if there's another license that is more common for Scala projects.

Something that doesn't complicate what can be done with the translated code

The license of what's being produce by the tool is not tied to the license of the tool itself. Just look at GCC. Its license is GPL, but the code produced by GCC can be whatever license you choose, including propritary.

[summer-alice]

I would like it to be Boost licensed. Unless there are any dependencies that prevent that.

I have no problems with the Boost license.

As for the dependencies: the org.eclipse.* are licensed under the EPL-1.0, same as DWT, however some newer versions use EPL-2.0. scala-io-file-2.11 doesn't seem to be around anymore, but the maven artifact shows it was licensed under the Scala License, which was BSD-3 Clause in 2014. ScalaTest is licensed under the Apache-2.0 license. So there shouldn't be any problems.

Something that doesn't complicate what can be done with the translated code

The license of what's being produce by the tool is not tied to the license of the tool itself. Just look at GCC. Its license is GPL, but the code produced by GCC can be whatever license you choose, including propritary.

Indeed, I was getting confused with the GPL linking exception.