Announcement Announcement Module
Collapse
No announcement yet.
STS 2.9.2 released Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by Martin Lippert View Post
    The "S" indicates the Spring nature of a project, but that shouldn't be added automatically for each project as long as there is no Spring involved. Do you use Spring in those projects? But it does sound like a bug that this nature got added automatically after you upgraded from 2.9.1 to 2.9.2. Can you send my such a project before it got updated? Maybe I can reproduce this issue somehow.
    Yes, I'm using it, and with that I mean there's a context xml file, and I use Spring components (classes, annotations, etc); but I do not use any Spring related tool in the IDE directly (no perspectives, and such).
    I'm sorry but - apart from being a commercial project - I have more than 70 projects in the workspace, and it would be impossible to get a stripped down version of anything

    Now that I recall a bit more, after moving to 2.9.2 all the projects stated that the Maven configuration was out of date, and that I had to update it. I guess the "S" replaced the original "J" after that.

    Originally posted by Martin Lippert View Post
    Regarding the slowdown: The Spring nature does indeed add additional functionality that is executed during a build. However, this should not cause your build to run for half an hour or so. I can see disc access in the thread dumps. Is your workspace on a local hard drive or on a network-attached storage? That could cause those slowdowns...
    Everything is local, from the workspace to the Maven local repository.

    This is the beginning of the context file:
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <beans xmlns="http://www.springframework.org/schema/beans"
    	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    	xmlns:context="http://www.springframework.org/schema/context"
    	xmlns:p="http://www.springframework.org/schema/p"
    	xmlns:util="http://www.springframework.org/schema/util"
    	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
    		http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util-3.0.xsd
    		http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd">
    
       <context:property-placeholder location="classpath:jdbc.properties"/>
       <context:annotation-config/>
       <context:component-scan base-package="my.web"/>
    Could there be something that makes STS to stop by?

    To add something more, I just reopened 2.9.2, cleaned the workspace and built everything.
    And it tells that "Project configuration is not up-to-date with pom.xml. Run project configuration update" on every project.

    And a bit more: going back to 2.9.1, after a clean and a build, all the projects maintained that "configuration not up-to-date", but after Maven -> Update Project Configuration everything is ok.
    Last edited by mayjay; May 30th, 2012, 10:06 AM.

    Comment


    • #17
      Hi Jkk,

      I'm sure you've got your belly full of this problem already. And I think the JVM crash is not very likely caused by SYS itself. STS doesn't have any 'native' code of its own. The problem is likely either an OpenJVM bug or, more likely, a problem in SWT Gnome bindings (native libararies that Eclipse uses for its GUI widgetry).

      Though in the strictest sense this is not an STS problem, it would be good if we could at least somehow try to determine who's problem it really is and if we can do so, follow up by filing a bug report in the right place.

      I'm willing to do a little more digging, but as a starting point I really need your *full* crash log.

      If its too much hassle to create Jira issues etc. I understand... so it is easiler for you, you can email it directly to me if you like.
      My email address is [email protected].

      Thanks,

      Kris

      Comment


      • #18
        Originally posted by Kris De Volder View Post
        Hi Jkk,

        I'm sure you've got your belly full of this problem already. And I think the JVM crash is not very likely caused by SYS itself. STS doesn't have any 'native' code of its own. The problem is likely either an OpenJVM bug or, more likely, a problem in SWT Gnome bindings (native libararies that Eclipse uses for its GUI widgetry).

        Though in the strictest sense this is not an STS problem, it would be good if we could at least somehow try to determine who's problem it really is and if we can do so, follow up by filing a bug report in the right place.

        I'm willing to do a little more digging, but as a starting point I really need your *full* crash log.

        If its too much hassle to create Jira issues etc. I understand... so it is easiler for you, you can email it directly to me if you like.
        My email address is [email protected].

        Thanks,

        Kris
        Oops, I didn't notice that the replies in this thread had gone to the second page so I didn't notice the new posts. Sorry. Anyway, I created a new bug report yesterday: https://issuetracker.springsource.com/browse/STS-2679 . Thanks for your help.

        Comment


        • #19
          sts2.9.2 installation problem

          hi, i am new in spring. when i double click on .exe file of sts, it shows an error box. which says, 'error:java.lang.reflect.InvocationTargetException '. what should i do.

          N.B: No eclipse ide or netbeans is running on my PC when i trying to install sts 2.9.2

          Comment


          • #20
            Hey!

            As said on this thread, please post more details there:
            http://forum.springsource.org/showth...lation-problem

            Thanks,
            Martin

            Comment


            • #21
              Problem Installing ADT 20.0.2 on STS 2.9.2

              An error occurred while collecting items to be installed
              session context wasprofile=com.springsource.sts.ide, phase=org.eclipse.equinox.internal.p2.engine.phase s.Collect, operand=, action=).
              No repository found containing: osgi.bundle,org.eclipse.cdt,8.0.2.201202111925
              No repository found containing: osgi.bundle,org.eclipse.cdt.codan.checkers,1.0.1.2 01202111925
              No repository found containing: osgi.bundle,org.eclipse.cdt.codan.checkers.ui,1.0. 0.201202111925
              No repository found containing: osgi.bundle,org.eclipse.cdt.codan.core,2.0.0.20120 2111925
              No repository found containing: osgi.bundle,org.eclipse.cdt.codan.core.cxx,1.0.0.2 01202111925
              No repository found containing: osgi.bundle,org.eclipse.cdt.codan.ui,2.0.1.2012021 11925
              .......

              I am using STS 2.9.2 and trying to install archive package of ADT 20.0.2. I even tried to install ADT 20.0.2 with online version but same error.

              Comment


              • #22
                Hey!

                The components that are mentioned in your error message belong to the Eclipse CDT package that is part of the Eclipse release. Please check if you have the Helios or Indigo update site enabled to let the install process grab those components from there (Preferences -> Update/Install -> Available Update Sites).

                If the standard Indigo or Helios (depending on the Eclipse version you are using for STS 2.9.2) is activated, then it could be a networking/connectivity problem (maybe). In that case, I would try again.

                If that also doesn't help, I would delete the p2 repo cache of your installation (something under the hood of the Eclipse installation implementation). Delete everything in here: sts-2.9.2.RELEASE/p2/org.eclipse.equinox.p2.repository

                HTH,
                Martin

                Comment

                Working...
                X