- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
java.rmi.Remote dependency
Mon, 2011-10-10, 14:53
Hi,
Following commit is very problematic for Scala+GWT project: https://github.com/paulp/scala-full/commit/bc2f054c21fb4f450ebf61e7cbc05bb090d97c3a
In nutshell, this commit introduces dependency on java.rmi.Remote for jvm compilation. It's regression compared to previous state of affairs where dependency on Remote stuff was declared lazily and evaluation would be triggered only when scala.remote annotation is used.
Can we get previous behaviour back?
--
Grzegorz Kossakowski
Following commit is very problematic for Scala+GWT project: https://github.com/paulp/scala-full/commit/bc2f054c21fb4f450ebf61e7cbc05bb090d97c3a
In nutshell, this commit introduces dependency on java.rmi.Remote for jvm compilation. It's regression compared to previous state of affairs where dependency on Remote stuff was declared lazily and evaluation would be triggered only when scala.remote annotation is used.
Can we get previous behaviour back?
--
Grzegorz Kossakowski
Sure. Oh I see, it's the map. (It didn't intentionally change the
laziness, but there's a little map and the one lazy drags in the
others.)
On Mon, Oct 10, 2011 at 6:53 AM, Grzegorz Kossakowski
wrote:
> Hi,
> Following commit is very problematic for Scala+GWT
> project: https://github.com/paulp/scala-full/commit/bc2f054c21fb4f450ebf61e7cbc05bb090d97c3a
> In nutshell, this commit introduces dependency on java.rmi.Remote for jvm
> compilation. It's regression compared to previous state of affairs where
> dependency on Remote stuff was declared lazily and evaluation would be
> triggered only when scala.remote annotation is used.
> Can we get previous behaviour back?
>
> --
> Grzegorz Kossakowski
>
>