- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
missing class files?
Tue, 2010-01-19, 02:03
Hi all,
I just updated my eclipse plugins to 2.8.0.r20558-b20100118020155, and
now compiling results in the error
| Description
| Resource | Path | Location | Type |
| class file needed by InterpreterLoop is missing.
| | | | |
| reference value jline of package refers to nonexisting
symbol. | stuff.model | | Unknown | Scala Problem |
Is a missing jline the problem? If so, can the dependency be removed?
I've tried getting jline to work in the eclipse RCP with little
success...
Cheers,
Mike
Tue, 2010-01-19, 04:27
#2
Re: missing class files?
On Mon, Jan 18, 2010 at 6:25 PM, Paul Phillips wrote:
> On Mon, Jan 18, 2010 at 05:03:01PM -0800, michael hohn wrote:
>> Is a missing jline the problem? If so, can the dependency be removed?
>> I've tried getting jline to work in the eclipse RCP with little
>> success...
>
> Yeah. I have no useful mechanism for knowing what does and doesn't
> depend on what else and no real way to anticipate this sort of thing. I
> added a repl history feature and there is a jline reference in
> InterpreterLoop where there wasn't one before.
>
> I can remedy that easily enough, but it would be unthrilling to have to
> defend against on an ongoing basis.
No problem. I just included the jline.jar as external dependency for
development for now.
> You don't need jline to work in the
> RCP by the way -- it's just that there's a reference to the class so the
> JVM insists it be resolvable. It won't load it.
So in the worst case, I'll provide a dummy class. Good enough.
Thanks!
Mike
Tue, 2010-01-19, 09:37
#3
Re: missing class files?
On Tue, Jan 19, 2010 at 1:03 AM, michael hohn wrote:
> I just updated my eclipse plugins to 2.8.0.r20558-b20100118020155, and
> now compiling results in the error
What are you trying to compile?
Cheers,
Miles
Tue, 2010-01-19, 13:57
#4
maven-scala-plugin: How to Generate Scaladocs?
Hello everyone,
I haven't done any Scala in a while and just noticed that my Scaladoc
generation via Maven doesn't work any longer.
I'm using the latest maven-scala-plugin, 2.13.1, and tried Scala
artifacts both of versions 2.8.0-SNAPSHOT and 2.8.0.Beta1-RC7.
The error message I get is:
>>>
[INFO] [scala:doc {execution: scala-doc}]
[INFO] Checking for multiple versions of scala
[INFO] Checking for multiple versions of scala
scalac error: Parameter '-bottom' is not recognised by Scalac.
scalac -help gives more information
scalac error: bad option: '-bottom'
scalac -help gives more information
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] wrap: org.apache.maven.reporting.MavenReportException: wrap:
Process exited with an error: 1(Exit value: 1)
<<<
Here is my POM snippet:
>>>
scala-doc
.pom-scala
org.scala-tools
maven-scala-plugin
scala-doc
verify
doc
org.apache.maven.plugins
maven-antrun-plugin
scala-doc-ant
verify
run
<<<
Any hints? This used to work, so what has changed?
Regards
---Phil
Tue, 2010-01-19, 14:37
#5
maven-scala-plugin: How to Generate Scaladocs?
Hello everyone,
I haven't done any Scala in a while and just noticed that my Scaladoc
generation via Maven doesn't work any longer.
I'm using the latest maven-scala-plugin, 2.13.1, and tried Scala
artifacts both of versions 2.8.0-SNAPSHOT and 2.8.0.Beta1-RC7.
The error message I get is:
>>>
[INFO] [scala:doc {execution: scala-doc}]
[INFO] Checking for multiple versions of scala
[INFO] Checking for multiple versions of scala
scalac error: Parameter '-bottom' is not recognised by Scalac.
scalac -help gives more information
scalac error: bad option: '-bottom'
scalac -help gives more information
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] wrap: org.apache.maven.reporting.MavenReportException: wrap:
Process exited with an error: 1(Exit value: 1)
<<<
Here is my POM snippet:
>>>
scala-doc
.pom-scala
org.scala-tools
maven-scala-plugin
scala-doc
verify
doc
org.apache.maven.plugins
maven-antrun-plugin
scala-doc-ant
verify
run
<<<
Any hints? This used to work, so what has changed?
Regards
---Phil
Tue, 2010-01-19, 17:27
#6
Re: maven-scala-plugin: How to Generate Scaladocs?
The commande line interface of scaladoc 2.8.0 is not compatible with
previous version. And the maven-scala-plugin will not be updated until
release of 2.8.
On Tue, Jan 19, 2010 at 14:30, Philip Köster wrote:
> Hello everyone,
>
> I haven't done any Scala in a while and just noticed that my Scaladoc
> generation via Maven doesn't work any longer.
>
> I'm using the latest maven-scala-plugin, 2.13.1, and tried Scala artifacts
> both of versions 2.8.0-SNAPSHOT and 2.8.0.Beta1-RC7.
>
> The error message I get is:
>
>>>>
>
> [INFO] [scala:doc {execution: scala-doc}]
> [INFO] Checking for multiple versions of scala
> [INFO] Checking for multiple versions of scala
> scalac error: Parameter '-bottom' is not recognised by Scalac.
> scalac -help gives more information
> scalac error: bad option: '-bottom'
> scalac -help gives more information
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] wrap: org.apache.maven.reporting.MavenReportException: wrap: Process
> exited with an error: 1(Exit value: 1)
>
> <<<
>
> Here is my POM snippet:
>
>>>>
>
>
> scala-doc
>
>
> .pom-scala
>
>
>
>
>
> org.scala-tools
> maven-scala-plugin
>
>
> scala-doc
> verify
>
> doc
>
>
>
>
>
> ! Create a jar for the Scaladoc files and install it
> ! in the local Maven repository
> -->
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> scala-doc-ant
> verify
>
>
> basedir="target/site/scaladocs"
>
> destfile="target/${project.artifactId}-${project.version}-scaladoc.jar"/>
>
> value="install:install-file"/>
> value="-DgroupId=${project.groupId}"/>
> value="-DartifactId=${project.artifactId}"/>
> value="-Dversion=${project.version}"/>
> value="-Dclassifier=scaladoc"/>
> value="-Dfile=target/${project.artifactId}-${project.version}-scaladoc.jar"/>
>
> value="-DgeneratePom=true"/>
> value="-DcreateChecksum=true"/>
>
>
>
>
> run
>
>
>
>
>
>
>
>
> <<<
>
> Any hints? This used to work, so what has changed?
>
> Regards
> ---Phil
>
>
>
Wed, 2010-01-20, 07:57
#7
Re: missing class files?
On Tue, Jan 19, 2010 at 12:27 AM, Miles Sabin wrote:
> On Tue, Jan 19, 2010 at 1:03 AM, michael hohn wrote:
>> I just updated my eclipse plugins to 2.8.0.r20558-b20100118020155, and
>> now compiling results in the error
>
> What are you trying to compile?
The following embedded scala toplevel, with a hacked-in classpath to all
RCP bundles I need access to.
This gives me a way to interactively develop new code while accessing
existing bundles, but if there is a cleaner approach I'd love to see
it.
As mentioned in my prior reply, this code now works again when the
jline.jar is added to the bundle as "external jar".
: class toplevel extends InterpreterLoop {
: override def main(settings: Settings) {
: this.settings = settings;
: createInterpreter();
: in = new SimpleReader;
: loadFiles(settings);
: }
: }
:
: object inferShell {
: var toplvl = new toplevel
:
: // Start interpreter.
: toplvl.main(Array("-Xnojline",
: "-classpath",
: "D:\\misc\\eclipse-modeling-galileo-SR1-incubation-win32\\eclipse\\configuration\\org.eclipse.osgi\\bundles\\734\\1\\.cp\\lib\\scala-library.jar..."
: ))
:
: val hasErrors = toplvl.interpreter.reporter.hasErrors
:
: def welcome = toplvl.printWelcome
:
: // Bind local variables.
: def bind(kvl : List[(String, Object)]) = {
: for ( (k,v) <- kvl) toplvl.injectOne(k, v)
: }
:
: // Start the repl.
: def repl = toplvl.repl
:
: // Sample main program.
: def main(args: Array[String]): Unit = {
: bind(List(
: ("a", int2Integer(1)),
: ("d", thing)
: ))
: repl
: }
:
: }
:
Cheers,
Mike
On Mon, Jan 18, 2010 at 05:03:01PM -0800, michael hohn wrote:
> Is a missing jline the problem? If so, can the dependency be removed?
> I've tried getting jline to work in the eclipse RCP with little
> success...
Yeah. I have no useful mechanism for knowing what does and doesn't
depend on what else and no real way to anticipate this sort of thing. I
added a repl history feature and there is a jline reference in
InterpreterLoop where there wasn't one before.
I can remedy that easily enough, but it would be unthrilling to have to
defend against on an ongoing basis. You don't need jline to work in the
RCP by the way -- it's just that there's a reference to the class so the
JVM insists it be resolvable. It won't load it.
def history = in match {
case x: JLineReader => Some(x.history)
case _ => None
}