[Randy]

hi,

– 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:

– Message Body ——————————-
I upgraded to the ME 4.0 M3 to see if the spring issues I was having with classpath/builder were fixed.

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

The interersting part is in the project view, the path is similier, but with a 3.9.310 in it.

Anyway, hope this helps. Holler if there is anything I can do to help in anyway.

BTW, is there a definition list of the above message icons? Ie an indicated usage?

TIA!

Randy

Edit:
Ok, it looks like the org.springframework.test classes are not avalable either. if I create a class, and add org.springframework., test is not an option.

If I expand the Spring 1.2 Testing Support Libs ME Lib object in the project view, it only has easymock.jar, easymockclassextenstion.jar, and junit.jar.

Also, at first I had 4.0 M2 installed, did an upgrade. had similer issues, so I uninstalled M2, then did a clean install of M3. M2 did have the missing libs. I followed the directions in a post in the install/config topic to remove ME (in eclpse, select help->software updates->manage config. select disable ME, shutdown eclipse, the rm -rf the MyEclipse install dir.

Also, what is the correct way to remove a spring capability from a project?

[Randy]

Figured it out. The spring libs appear to be misconfigured (ie point to the previous release).

From the eclipse menubar, select Window->Preferences
Then expand out the MyEclipse option, expand the Project Capabilities Option and select Spring.

For each Library Module, note the paths. it has *211* and not *310 in it. Also the spring testing support library module is missing the spring-mock.jar which has the spring related extensions for Junit. It appears that I can add this jar manually, but it will not let me edit the existing paths for the other jars.

[David Orriss Jr]

I clicked “Restore Defaults” on that dialog and all of the Spring library entries were reset to were they are supposed to be pointing…

EDIT: Minor correction… it does update the path data but I still get the error that MyEclipse “cannot access the build path” if I try to put the spring libs on the build path. If I try to copy them *into* the project that works fine…

Oh another note the “Spring All” entry that uses the Spring.jar and provides any dependences required needs to come back. I don’t worry about having the level of modularity that you guys configured.. so I know I have to check all of them when I want to add them to my project…

Of course, I know I can always make a user lib entry and add that, so it’s all good I suppose..

[support-michael]

I have entered a problem-report to reevaluate the library/plugin upgrade mechanism to ensure that all paths stored are plugin-relative and self updating.

Oh another note the “Spring All” entry that uses the Spring.jar and provides any dependences required needs to come back. I don’t worry about having the level of modularity that you guys configured.. so I know I have to check all of them when I want to add them to my project…

There was a problem in M2 with the “Spring All” library that it only added the spring-all.jar to the project buildpath. None of the many dependent jars were included. This caused some Spring users to experience compilation and runtime deployment problems with ClassNotFoundExceptions. We discussed this possibility of reintroducing the “Spring All” library and decided if so it will be comprehensive with spring-all.jar and all of its dependent jar (there are a lot of them) – not sure most devs will appreciate this especially during deployment. If the many jars is undesirable then a smaller subset will require editing the the library and removing the unwanted jars.

So with M3 we backed up and looked at the basic Spring libraries and tried to get them right as “Spring All” is the aggregation of them all.

[Randy]

I’ve verified that the Restore Defaults fixes a lot of the pathing.

I’ve did have to create a new library for some missing springlibs, including spring-hibernate.jar and spring-orm.jar. spring-mock.jar is now showing up in the spring-testing one (not sure if I did it since I did switch to my real project).

Happy to confirm the M2 bug with the junit stuff is now resolved! whoohoo!

Tx everyone.

R

[support-michael]

Good catch on the missing ORM library. I think it was temporarily pulled from M3 for some reason that I’m not aware of. I’ve created a problem report that dev team acknowleges will be addressed in the GA release.

[Randy]

hi,
Could you please add the spring-hibernate.jar to the list of missing libs. Once I added this, I got my stuff from jbuilder working.

Tx!
Randy

[support-michael]

Hi Randy,

The reason the Spring-ORM/hibernate.jars were omitted in M3 is that ME provides the “Add Hibernate Capabilites” which handles providing these libraries on the buildpath. Per the comment prior to this we will be adding the ORM library with hibernate jars. So I’m marking this as a +1 for that idea. After 4.0GA the dev team will be expanding ME’s Hibernate support to work directly with Spring as well as standalone.

Thanks for your feedback.

Regards,

[Randy]

Sweet! Sounds like a pretty good plan. It never occurred to me about the add hibernate props. doh!

R

[Author]

Posts