Announcement Announcement Module
Collapse
No announcement yet.
STS 2.5.2 wants to load upgraded Roo-project in previous version Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • STS 2.5.2 wants to load upgraded Roo-project in previous version

    I successfully completed all the steps described at http://static.springsource.org/sprin...ml#upgrade-any in my Roo 1.1.1 created project.

    STS keeps opening the project as 1.1.1 and won't let me chose 1.1.2. Anyone else is seeing this? Any ideas how to prevent it?
    I've marked the 1.1.2 version as the preferred version.

  • #2
    problem stays with 2.5.2SR2 and 2.6.0M1

    Now I get multiple
    java.lang.NullPointerException
    at start, also in 2.5.2 SR1 and 2.6.0M1 as well. Error log from the latter after ""Initialize CompilationUnit Manager", "Initializing Java Tooling", "Initializing classpath usage monitoring":
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] java.lang.NullPointerException
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.maven.ide.eclipse.jdt.internal.MavenClasspathC ontainerInitializer.initialize(MavenClasspathConta inerInitializer.java:43)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaModelManager.ini tializeContainer(JavaModelManager.java:2707)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaModelManager.get ClasspathContainer(JavaModelManager.java:1850)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.core.JavaCore.getClasspathContaine r(JavaCore.java:2705)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaProject.resolveC lasspath(JavaProject.java:2645)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaProject.resolveC lasspath(JavaProject.java:2783)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaProject.getResol vedClasspath(JavaProject.java:1915)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaProject.buildStr ucture(JavaProject.java:440)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.Openable.generateInf os(Openable.java:258)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaElement.openWhen Closed(JavaElement.java:515)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaElement.getEleme ntInfo(JavaElement.java:252)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaElement.getEleme ntInfo(JavaElement.java:238)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaElement.getChild ren(JavaElement.java:193)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.jdt.internal.core.JavaProject.getPacka geFragmentRoots(JavaProject.java:1803)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.springframework.ide.eclipse.internal.uaa.monit or.LibraryUsageMonitor.projectClasspathChanged(Lib raryUsageMonitor.java:169)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.springframework.ide.eclipse.internal.uaa.monit or.LibraryUsageMonitor.access$0(LibraryUsageMonito r.java:165)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.springframework.ide.eclipse.internal.uaa.monit or.LibraryUsageMonitor$2.run(LibraryUsageMonitor.j ava:122)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.core.internal.jobs.Worker.run(Worker.j ava:54)
    2011-03-03 12.21.10 [0x0-0x39ad9aa].com.springsource.sts[87503] at org.eclipse.core.internal.jobs.Worker.run(Worker.j ava:54)
    and
    Problems occurred while trying to save the state of the workbench.
    Problems occurred during save.
    org/maven/ide/eclipse/jdt/internal/MavenClasspathContainerSaveHelper
    at STS quit.

    When I try Open Roo shell for existing projects, some projects are white containing no text (see attachment) in the Roo Shell Project Selection dialog and none of them are openable within STS with Roo 1.1.2.

    The project in question – which I have prepared for Roo 1.1.2– does open in Roo 1.1.2 from the command line in Terminal and can run the project in Tomcat with perform maven command. I suspect there are some incompatibilities between my workspace, Roo 1.1.2 and possibly something other related to STS, but I'm not sure on what it is.

    I'm going to try STS 2.6.0 M2, changing workspace and reimporting the project. But suggestions are welcome.
    I realize this may be a pure STS problem, but as it's natural to use Roo with STS I suppose this post belong here as far as the Roo connection is valid for this problem.
    Last edited by MiB; Mar 3rd, 2011, 06:00 AM.

    Comment


    • #3
      another interesting discussion with similar symptoms with 1.1.2

      When reading the thread Roo 1.1.2 addon upgrade all looks like not working on Win7 I realized I also saw this initially in Terminal when running Roo 1.1.2, but I did not try and upgrade anything.

      Interesting enough the errors reported in that thread also includes java.lang.NullPointerException albeit in a seemingly different context.

      Comment


      • #4
        solved in STS 2.6.0.M2

        I installed Springsource Tools Suite 2.6.0.M2 and reinstalled Roo 1.1.2 along with it and this problem is gone also with the same workspace and identical projects. Hopefully the M2 version is more stable than M1.
        I'm still not sure why 2.5.2.SR1 couldn't work just as well with Roo 1.1.2. I'll revisit it later.

        Comment

        Working...
        X