Can't seem to move past 1939

I again tried to move up, this time to 1994. After refreshing my maven projects, the plugin created the facets, but did not assign a scala compiler.

I specify


      <dependency>
        <groupId>org.scala-lang</groupId>
        <artifactId>scala-library</artifactId>
        <version>2.8.0</version>
      </dependency>
      <dependency>
        <groupId>org.scala-lang</groupId>
        <artifactId>scala-compiler</artifactId>
        <version>2.8.0</version>
        <scope>compile</scope>
      </dependency>


Should I expect that that plugin would configure the facet with this compiler as it used to?

Well, I was willing to set it manually, but my options to do so look like:

ScreenHunter_01 Aug. 10 11.10.gif


I have these errors in the log:

2010-08-10 11:04:15,663 [92693564]  ERROR - ij.components.ComponentManager - Not disposed pointer: listener=null
url=jar://C:/Users/bkaplan/.m2/repository/ch/qos/logback/logback-core/0.9.24/logback-core-0.9.24-javadoc.jar!/
Creation trace null

java.lang.RuntimeException: Not disposed pointer: listener=null
url=jar://C:/Users/bkaplan/.m2/repository/ch/qos/logback/logback-core/0.9.24/logback-core-0.9.24-javadoc.jar!/
Creation trace null

 at com.intellij.openapi.vfs.impl.VirtualFilePointerImpl.throwNotDisposedError(VirtualFilePointerImpl.java:104)
 at com.intellij.openapi.vfs.impl.VirtualFilePointerManagerImpl.assertPointersDisposed(VirtualFilePointerManagerImpl.java:331)
 at com.intellij.openapi.vfs.impl.VirtualFilePointerManagerImpl.disposeComponent(VirtualFilePointerManagerImpl.java:322)
 at com.intellij.openapi.components.impl.ComponentManagerImpl.disposeComponents(ComponentManagerImpl.java:155)
 at com.intellij.openapi.application.impl.ApplicationImpl.dispose(ApplicationImpl.java:432)
 at com.intellij.openapi.util.Disposer$1.execute(Disposer.java:37)
 at com.intellij.openapi.util.Disposer$1.execute(Disposer.java:35)
 at com.intellij.openapi.util.objectTree.ObjectNode$1.execute(ObjectNode.java:126)
 at com.intellij.openapi.util.objectTree.ObjectNode$1.execute(ObjectNode.java:108)
 at com.intellij.openapi.util.objectTree.ObjectTree.executeActionWithRecursiveGuard(ObjectTree.java:154)
 at com.intellij.openapi.util.objectTree.ObjectNode.execute(ObjectNode.java:108)
 at com.intellij.openapi.util.objectTree.ObjectTree.executeAll(ObjectTree.java:136)
 at com.intellij.openapi.util.Disposer.dispose(Disposer.java:94)
 at com.intellij.openapi.util.Disposer.dispose(Disposer.java:90)
 at com.intellij.openapi.application.impl.ApplicationImpl.d(ApplicationImpl.java:244)
 at com.intellij.openapi.application.impl.ApplicationImpl.access$100(ApplicationImpl.java:81)
 at com.intellij.openapi.application.impl.ApplicationImpl$9.run(ApplicationImpl.java:639)
 at com.intellij.openapi.application.impl.ApplicationImpl.exit(ApplicationImpl.java:647)
 at com.intellij.openapi.application.impl.ApplicationImpl.exit(ApplicationImpl.java:616)
 at com.intellij.openapi.wm.impl.IdeFrameImpl$2$1.run(IdeFrameImpl.java:162)
 at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:319)
 at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
 at com.intellij.ide.IdeEventQueue.f(IdeEventQueue.java:610)
 at com.intellij.ide.IdeEventQueue.b(IdeEventQueue.java:500)
 at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:368)
 at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
 at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
2010-08-10 11:04:15,697 [92693598]  ERROR - ij.components.ComponentManager - IntelliJ IDEA 9.0.3  Build #IU-95.429
2010-08-10 11:04:15,698 [92693599]  ERROR - ij.components.ComponentManager - JDK: 1.6.0_20
2010-08-10 11:04:15,699 [92693600]  ERROR - ij.components.ComponentManager - VM: Java HotSpot(TM) 64-Bit Server VM
2010-08-10 11:04:15,699 [92693600]  ERROR - ij.components.ComponentManager - Vendor: Sun Microsystems Inc.
2010-08-10 11:04:15,699 [92693600]  ERROR - ij.components.ComponentManager - OS: Windows 7
2010-08-10 11:04:15,699 [92693600]  ERROR - ij.components.ComponentManager - Last Action: Vcs.UpdateProject



Does nobody else seem to have these problems? How can it be only me?
0
12 comments

the plugin is broken above 1939 for about anyone i think. 2000 also doesn't fix the (my) problems

0

Previous versions of the plugin considered "scala-compiler" dependency as a Scala compiler, that was a misbehavior.
Dependency on "scala-compiler" artifact has nothing to do with Scala compiler.
See this message for details.

0

May I see a pom.xml that is causing these troubles (including ones with encoding)?

0

Sorry Pavel, my pom also has:

      <plugin>
        <groupId>org.scala-tools</groupId>
        <artifactId>maven-scala-plugin</artifactId>
        <configuration>
          <jvmArgs>
            <jvmArg>-Xms256m</jvmArg>
            <jvmArg>-Xmx1024m</jvmArg>
            <jvmArg>-DdisplayCmd=true</jvmArg>
          </jvmArgs>
          <compilerPlugins>
            <compilerPlugin>
              <groupId>net.virtualvoid</groupId>
              <artifactId>${scala.enhanced.strings.artifactId}</artifactId>
              <version>${scala.enhanced.strings.version}</version>
            </compilerPlugin>
          </compilerPlugins>
        </configuration>
      </plugin>


I don't specify the goals or the scala version like in the thread you referenced, but the plugin is indeed executed for those goals with the correct version so I assume they are the defaults.

Just to be clear, in that thread you referenced you said:

"Such declaration should be automatically imported by IDEA as a Scala compiler library for facet.
(regular dependencies, like scala-library, should be imported as well - as entries in module dependencies list)."

So, with the above I should NOT have to specify the compiler in every module via the facet, correct? If so, this is not the behavior I am seeing. But I'll try adding the goals and the configuration sections and see if that helps.
0

What do you mean by "encoding"?

0

My iml file have the following:


  <component name="FacetManager">
    <facet type="scala" name="Scala">
      <configuration>
        <option name="compilerLibraryLevel" value="Project" />
        <option name="compilerLibraryName" value="maven: org.scala-lang:scala-compiler:2.8.0" />
      </configuration>
    </facet>
  </component>



Which looks to be correct. I can start FSC and it seem to be up and running ok. But when I try to compile I get a popup saying



  "Please, adjust compiler library in Scala facet: multiple scala-compiler-*.jar's attached."



mvn dependency:tree shows this is not the case.



Anyway I have attached all my poms and the ipr and iml files for the project.



-bary


Attachment(s):
p.tar
0

Pavel, is there anything I can provide?

0

I'm working on import right now, the project sample you attached was a great help to me.
Maven import is becoming significantly better :).

0

Thank you, thank you!

0

You are welcome. Check the next nightly build.

(your project deals with all possible technologies at once, looks like some AI implementation :))

0

I'm back on the edge! I've been able to upgrade to 2026. The scala-compiler in the module setting still displays as corrupt (ie, the squares) but all seems to work. I'm assuming that that corruption is an issue with Idea/Maven, as I see it in the maven dependency tree view as well. (Actually, thats the first time I saw the problem.)

Thanks Pavel!!

0

One downside however is that if I even open the module settings then all the Idea message from that point are little squares. For example after doing  a full build the popup that would say the build completed is a string squares. Of course this would also be the case if I [tried to] viewed the maven dependency tree. Restarting Idea clears things up.

0

Please sign in to leave a comment.