4.0 M3 has bad paths for spring libs. [Duplicate]

Hi,
I started a thread on this in the general discussion area before I figured it was actually a bug. Here is a reference to the original post:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-8524.html

– System Setup ——————————-
Operating System and version: GentooLinux
Eclipse version: 3.1
Eclipse build id: 20050627-1435
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: subclipse, doclipse
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8 (4 jars, 4 dirs)
MyEclipse version: 4.0 M3
Eclipse JDK version: sun 1.5
Application Server JDK version:
Are there any exceptions in the Eclipse log file? notlog found

If this is a DB related question please answer the following:

RDBMS vendor and version:
JDBC driver vendor and version, and access type (thin, type-2, etc):
Connection URL:
Eclipse error logs related to com.genuitec.eclipse.sqlexplorer packages:
Anyway, to summerize. I’ve found two problems with a clean install of ME 4.0. When I create a project, and then try to add the Spring capability to it, it barfs. From the link above:
I decided to start a new project and add Spring support to it. this fails. Steps:
create the new project.
Right click on the project in the package explorer, then select MyEclipse->Add Spring Capabilities.

I then select Spring AOP, Core, DAO, Support, and testing libraries. I have the add checked to project build-path.

I select next, toggle the new spring fconfig file. Select the Browse button next to the folder field, select src, add new dir called conf. select conf and then click on OK. Enter name appContext.xml. Finish

I then get a dialog “Spring Install Problems” Reason: Unable to access project’s build path.

It looks like the spring capability got added, but no spring objects are in the buildpath. I can add these manually from the looks of things by rightclick on the project->buildpath->Configure I then select the add Library, and from the select box select MyEclipse. All of the spring libs are now visible in the project package explorer view. But there is a red X next to the project. If I look in the Problems tab, I see this:
Severity Description Resource In Folder Location Creation Time
2 Project SpringTesting is missing required library: ‘/usr/local/randy/MyEclipse/eclipse/plugins/com.genuitec.eclipse.springframework_3.9.211/data/1.2/lib/spring-aop.jar’ SpringTesting August 15, 2005 1:11:26 PM
2 Project SpringTesting is missing required library: ‘/usr/local/randy/MyEclipse/eclipse/plugins/com.genuitec.eclipse.springframework_3.9.211/data/1.2/lib/spring-core.jar’ SpringTesting August 15, 2005 1:11:26 PM
2 Project SpringTesting is missing required library: ‘/usr/local/randy/MyEclipse/eclipse/plugins/com.genuitec.eclipse.springframework_3.9.211/data/1.2/lib/spring-dao.jar’ SpringTesting August 15, 2005 1:11:26 PM
2 The project cannot be built until build path errors are resolved SpringTesting August 15, 2005 1:11:26 PM

Looking into this, I found I could then add the library objects for these spring components manually via the project build path tool. Problem was that these actually have paths that point to the M2? release. Note the .211 in the path. I verified this in the Window->Preferences-ME-Project capabilities->Spring and checked out the paths for the Library objects.

Also, the spring-mock.jar is missing from the testing support spring library.