Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: Build Path is Incomplete. Cannot Find....

  1. #11
    Join Date
    Jul 2008
    Location
    Dundee, Scotland
    Posts
    6

    Default

    I can confirm that myself & three of my colleagues have also been seeing this issue while using STS 2.3.1 & 2.3.2 over the last few months.

    To date we cannot find a specific pattern as to when the errors will appear / how to correctly resolve the issue (although we will try the workaround suggested by bcoffe)... sometimes a simple project clean / STS restart seems to fix the issue, other times doing bizzare things like installing & uninstalling plugins seems to resolve the issue but none of these work consistently.

    It can quite often happen once we've done a fresh install of STS, created a new workspace, and then re-imported all of our existing projects.

    In addition it sometimes requires a "fake edit" of the bean configuration files (select all, cut, save, paste, save) before the errors will disappear.

    If you need any more info just give me a shout.

  2. #12
    Join Date
    Jul 2008
    Location
    Dundee, Scotland
    Posts
    6

    Default

    Quote Originally Posted by jamiecramb View Post
    I can confirm that myself & three of my colleagues have also been seeing this issue while using STS 2.3.1 & 2.3.2 over the last few months.

    To date we cannot find a specific pattern as to when the errors will appear / how to correctly resolve the issue (although we will try the workaround suggested by bcoffe)... sometimes a simple project clean / STS restart seems to fix the issue, other times doing bizzare things like installing & uninstalling plugins seems to resolve the issue but none of these work consistently.

    It can quite often happen once we've done a fresh install of STS, created a new workspace, and then re-imported all of our existing projects.

    In addition it sometimes requires a "fake edit" of the bean configuration files (select all, cut, save, paste, save) before the errors will disappear.

    If you need any more info just give me a shout.
    I can confirm that replacing the 2.3.2 versions of the following jars with the 2.3.0 versions provides a workaround for this issue in STS 2.3.2:

    sts-2.3.2.RELEASE/plugins/org.springframework.ide.eclipse.aop.core_2.3.2.201 003220227-RELEASE.jar
    sts-2.3.2.RELEASE/plugins/org.springframework.ide.eclipse.aop.mylyn_2.3.2.20 1003220227-RELEASE.jar
    sts-2.3.2.RELEASE/plugins/org.springframework.ide.eclipse.aop.ui.matcher_2.3 .2.201003220227-RELEASE.jar
    sts-2.3.2.RELEASE/plugins/org.springframework.ide.eclipse.aop.ui_2.3.2.20100 3220227-RELEASE.jar

  3. #13
    Join Date
    Aug 2004
    Location
    Duesseldorf, Germany
    Posts
    1,210

    Default

    Hi,

    (sorry, I just back from vacation).

    This error message is a bit strange as this should really be fixed in STS 2.3.2. In all my tests it is fixed and never occurred again. Could someone please provide steps to re-produce with a vanilla STS download? And maybe share a project that shows the issue.

    Also replacing the aop 2.3.2 jars with the ones from 2.3.0 can't solve this issues because the 2.3.0 jars are API incompatible with required dependencies from 2.3.2 that are not replaced. So there is something else going on here as otherwise you guys would see a lot of NoSuchMethodErrors in your Error Log.

    Regards, Christian
    Christian Dupuis
    SpringSource, a division of VMware
    Lead, SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/cdupuis

  4. #14
    Join Date
    Jun 2008
    Location
    Zurich, Switzerland - Freiburg i. Breisgau, Germany
    Posts
    102

    Unhappy

    I have also installed STS 2.3.2 on Eclipse 3.4 under Windows and I am having the same problem.
    Here the petclinic-servlet.xml and applicationContext-jdbc.xml is complaining missing class files (org.springframework.samples.petclinic.web.ClinicB indingInitializer, org.springframework.samples.petclinic.web.VisitsAt omView, org.springframework.samples.petclinic.jdbc.SimpleJ dbcClinic and org.springframework.samples.petclinic.aspects.Call MonitoringAspect) though it is in the src folder.
    Tai Truong
    pointsoftware.ch

  5. #15
    Join Date
    Aug 2004
    Location
    Duesseldorf, Germany
    Posts
    1,210

    Default

    ttruong,

    can you point to the sample project you are using? Maybe that I'm able to re-create.

    Thanks,

    Christian
    Christian Dupuis
    SpringSource, a division of VMware
    Lead, SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/cdupuis

  6. #16
    Join Date
    Jun 2008
    Location
    Zurich, Switzerland - Freiburg i. Breisgau, Germany
    Posts
    102

    Default

    I did the following to install STS 2.3.2:

    1. Import the update sites from the bookmarks.xml (following the spring instructions)
    2. I installed the 7 plugins from the site http://www.springsource.com/update/e3.5:
    - Core / dm Server Tools
    - Core / Spring IDE
    - Core /STS
    - Extensions (Incubation) / Spri
    - Extensions / Spring IDE
    - Extensions / STS
    - Integrations / Spring IDE

    3. In eclipse using svn I checked out the petclinic project from src.springframework.org/svn/spring-samples/petclinic/trunk
    Once the project is in the workspace maven downloads all related dependencies.
    At the end I am having the build path problems in those two xml files.
    Tai Truong
    pointsoftware.ch

  7. #17
    Join Date
    Jun 2008
    Location
    Zurich, Switzerland - Freiburg i. Breisgau, Germany
    Posts
    102

    Default

    Cleaning the project didn't work but when restarting eclipse the error problem disappears. That is weird.
    Tai Truong
    pointsoftware.ch

  8. #18
    Join Date
    Feb 2006
    Posts
    20

    Default

    Have similar issue with STS 2.3.2. I was able to get rid of the issue by checking out to workspace missing projects "in the middle". Let me explain:

    - Project A (uses classes in application context) from Project B
    - Project B has dependency to Project C

    In my workspace I had following projects:
    - Project A
    - Project C

    After I checked out Project B to workspace and cleaning Project A - no more issues. I'm not sure how it works but maybe:

    - Project A finds required class from Project B in JAR file,
    - Project A tries to find class from Project C also in JAR file. Instead it should look for it in Eclipse project dependencies.

  9. #19
    Join Date
    May 2008
    Posts
    14

    Default

    This is still happening in STS 2.7.1.RELEASE. @rience gave me the clue to just clean ALL of my projects and that cleared it up, but still annoying. Is there an issue filed for this already?

  10. #20
    Join Date
    Sep 2008
    Location
    Hamburg, Germany
    Posts
    1,650

    Default

    Hey!

    Depending on what the problem really is. We have plans to upgrade m2e to the new Eclipse hosted version 1.0 in the near future, so that hopefully solve this.

    -Martin
    Martin Lippert
    SpringSource, a division of VMware
    SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/martinlippert

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •