#1000820
- Created on2011-12-23 19:39
- Reported by
- StatusFixed
- PriorityHighest (1)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
PC doesn't honor the JDK classpath [Scalac within Eclipse cannot see new method toPath() in java.io.File]
I switched my project to use JDK 7 by selecting the Java 7 environment in project properties. However, although the Scala compiler could see the new NIO2 classes, it couldn't see a new method toPath() on java.io.File.
This problem does not occur with scalac 2.8.1 on the command line.
This problem does not occur with scalac 2.8.1 on the command line.
Leave a comment
It looks like the presentation compiler isn't honoring the JDK classpath (but the build compiler does, so there are no build errors).
on 2012-05-10 14:05 *
By Iulian Dragos
Component changed from Eclipse to Presentation Compiler
Priority changed from Normal (3) to Highest (1)
Summary changed from Scalac within Eclipse cannot see new method toPath() in java.io.File to PC doesn't honor the JDK classpath [Scalac within Eclipse cannot see new method toPath() in java.io.File]
on 2012-05-11 17:40 *
By Iulian Dragos
Assigned to set to login
Status changed from Accepted to Fixed
(In revision:ab2137e1e5fc23dc3ffbb2139303df044bd99ed1) Use the configured JDK when instantiating the presentation compiler.
The Scala compiler adds the currently running JDK to the class path, taking precedence over the JDK
configured in the build path. This commit fixed #1000820, and generalizes the scheme used by the Sbt
builder.
Branch: master
The Scala compiler adds the currently running JDK to the class path, taking precedence over the JDK
configured in the build path. This commit fixed #1000820, and generalizes the scheme used by the Sbt
builder.
Branch: master
on 2012-05-11 17:48 *
By Iulian Dragos
(In revision:d396d982063107bd185b9f3c66fe8139507dfecd) Use the configured JDK when instantiating the presentation compiler.
The Scala compiler adds the currently running JDK to the class path, taking precedence over the JDK
configured in the build path. This commit fixed #1000820, and generalizes the scheme used by the Sbt
builder.(cherry picked from commit ab2137e1e5fc23dc3ffbb2139303df044bd99ed1)
Branch: release/scala-ide-2.0.x
The Scala compiler adds the currently running JDK to the class path, taking precedence over the JDK
configured in the build path. This commit fixed #1000820, and generalizes the scheme used by the Sbt
builder.(cherry picked from commit ab2137e1e5fc23dc3ffbb2139303df044bd99ed1)
Branch: release/scala-ide-2.0.x
on 2012-05-12 14:40 *
By Iulian Dragos
(In revision:ab2137e1e5fc23dc3ffbb2139303df044bd99ed1) Use the configured JDK when instantiating the presentation compiler.
The Scala compiler adds the currently running JDK to the class path, taking precedence over the JDK
configured in the build path. This commit fixed #1000820, and generalizes the scheme used by the Sbt
builder.
Branch: platform/juno
The Scala compiler adds the currently running JDK to the class path, taking precedence over the JDK
configured in the build path. This commit fixed #1000820, and generalizes the scheme used by the Sbt
builder.
Branch: platform/juno
on 2012-06-28 21:33 *
By Mirco Dotta
Fixed in version set to 2.0.2
Eclipse version changed from Indigo to Indigo - Eclipse 3.7