Depending on your maven version, this is probably due to JLine + OSGi classpath magic not working nicely together. In fact, currently that should *not* be happening with 2.8.0-SNAPSHOT because jline does not show up with the scala-compiler.
On Thu, Jun 11, 2009 at 10:35 AM, Naftoli Gugenheim
<naftoligug@...> wrote:
I don't know if this is relevant, but when I have the eclipse scala builder enabled and run a maven build from eclipse with the maven scala plugin, I get an error along the lines that _jline.dll was already loaded in the classloader.
From: Josh Suereth <joshua.suereth@...>
Sent: Wednesday, June 10, 2009 8:59 AMTo: scala-tools scala-tools <scala-tools@...>; maven-and-scala@...
Subject: [scala-tools] Adding dependency on jline to compiler pom
Does anyone have any reason why we should *not* add the jline artifact as a dependency of scala-compiler from 2.8.0 on? I believe it's an optional dependency, but adding it in the pom will make life easier for maven-repo-aware dependency managers.
-Josh
