Mar 27th, 2010, 02:06 PM
Build Path is Incomplete. Cannot Find....
I have been happily working with Mac OSX Snow Leopard 10.6.2, Spring 3.0, Eclipse 3.5, Maven 2, and STS 2.3.0 for about 2 months.....then I upgraded to Spring 3.0.1, Eclispe 3.5.2, and STS 2.3.2 and I have had a nightmare of problems since.
Here is what I did:
- Downloaded new Eclipse 3.5.2 Java EE edition from Eclipse.org.
- Installed all the patches and added XML and XSL plugins
- Installed Spring Tool Suite 2.3.2 following directions on Springs Web Site
- Installed m2Eclipse
Now all my config.xml files show this error for anything to do with Database transactions:
"Build Path is incomplete. Cannot find class file or could not initialize class org.springframework.aop.aspectj.AspectJExpressionP ointcut"
I have narrowed down the problem to the spring transaction lines of code. Comment these lines out and the file will not have any errors, uncomment all the errors show up again.
<bean id="transactionManager" class="org.springframework.orm.hibernate3.Hibernat eTransactionManager">
<property name="sessionFactory" ref="sessionFactory" />
<tx:annotation-driven transaction-manager="transactionManager" />
Again, code worked perfectly before upgrade, doesn't work now. I have pulled my hair out for two days trying to solve this and can't figure it out. Any help would be appreciated. (I think it has something to do Maven, but can't figure out what)
Mar 29th, 2010, 12:48 PM
It smells like m2eclipse doesn't see hibernate on your build path. I "upgraded" from STS 2.3.0 to 2.3.1 and had similar issues. The short story is that the previous version of m2eclipse seems to have worked a lot better - and/or the upgrade process breaks existing projects? There is a related thread http://forum.springsource.org/showthread.php?t=86012. I actually ended up downloading 2.3.1 and installing from scratch to try to overcome the issue to no avail, which suggests that the 0.10 version of m2eclipse is broken. I have not resolved the issue, nor have I figured out how to downgrade back to 2.3.0.
Mar 29th, 2010, 01:40 PM
I think you are very likely correct. Fortunately I have the previous version of Eclipse (3.5.1), STS (2.3.0), and M2Eclipse(0.9.8) on our server. When I use the old configuration, the project works. But when I use the new stuff it breaks as I mentioned above.
Currently I'm trying to uninstall m2eclipse 0.10 and replace it with the old one (0.9.8) but keeping the new STS (version 2.3.2).
Mar 30th, 2010, 08:14 AM
I think I have found a work around here it is. Note that this is NOT A SOLUTION but will get you back working. I wish someone from springsource would take a look at this because I think this is likely a bug.
- Open up your Eclipse->Plugins directory
- Replace all the org.springframework.ide.eclipse.aop...2.3.2 JAR files with the old 2.3.0 jar files (if you still have them!)
- Open up Eclipse
- Should be working now (sort of)
No more compilation errors, but also no more Spring IDE pretty graphics showing you the crosscutting in the Spring Configuration XML files. But it seems to be crosscutting and actually working, even though the IDE doesn't have any indication of the crosscutting.
Again really wish someone from Spring would take a look. I can't be the only one experiencing this problem as I have a very simple project and did a basic upgrade.
Mar 30th, 2010, 04:59 PM
I wish I had a better answer for you, but perhaps the best solution is to start from a fresh install of STS 2.3.2 rather than starting from Eclipse 3.5.2 and installing STS from there.
Christian, the STS lead is on vacation this week and if you wait until he comes back, then he may have a better answer for you.
Mar 30th, 2010, 05:39 PM
The Mystery Deepens.....
So yes Andrew, I also tried just downloading STS 2.3.2 directly from spring and got the exact same problem, namely the application-config.xml said the Build path was incomplete and could not find org.springframework.ide.eclipse.aop.aspect....etc. .
But here is something interesting that happened now:
After applying my before mentioned work around on my Development Desktop (Mac Pro, Mac OS X 10.6.2). I then was going to do the same thing with my laptop (MacBook Pro Mac OS X 10.6.3). So I deleted all my old eclipses and old workspaces (as I had done many times already while trying to solve this problem.) Then opened my new Eclipse (the same one that wasn't working before on the laptop) and checked out all the code from subversion again. Now magically everything on the laptop is working! And this is before applying my workaround mentioned before.
Just in case you think this may be because someone else on the team made a change that fixed the problem and then I checked out the fix. I also tried creating a maven project which used the <tx:annonotations> stuff from scratch and got the same errors as our main project and now those errors are also seemingly magically gone.
Mar 30th, 2010, 06:01 PM
So, you are saying that you have different behavior when you check out the svn project in a clean workspace than from when upgrade your project in an existing workspace?
Is that the difference between your two scenarios?
Mar 30th, 2010, 06:08 PM
Yes & No...
Originally when I posted....Same problem on all computers using STS 2.3.2 no matter what I tried. Tried checking out project into new workspace, delete all the old workspaces, tried using STS download etc....never worked until I applied the workaround mentioned before.
Now the behavior seems to have somehow fixed itself on all the machines since I applied the workaround on one machine and then rechecked out the code from subversion on the other machines.
But the code has always worked no matter what so long as it was running on STS 2.3.0 and it continues to still work on those machines.
Mar 30th, 2010, 06:16 PM
If your problem returns, please let us know.
Apr 6th, 2010, 07:28 AM
I'm still continuing to have this problem it seems to show back up randomly. The only solution seems to replace the 2.3.2 AOP jar's with 2.3.0 AOP Jar's. I would really like to have a solution for this. Is know one else experiencing this?
Tags for this Thread