[davout]

I’ve encountered a situation recently where adding both ‘Spring 2.0’ and ‘Hibernate 3.0’ capabilities introduced a jar conflict (in this case asm.jar).

Through chasing down this issue I’ve noticed a logical flaw in how MyEclipse manages the association of jars to capabilities.

To correct my own problem I’ve had to modify the system level defaults as set under the ‘Windows/Preferences’ dialog in the ‘MyEclipse/Project capabilities tab. This seems wrong – to correct a project level capability conflict I am making adjustments
at a system level.

I think a better approach would be to have some equivalent capability jar inclusion/exclusion definition facilities at a project level. These project level facilities would use the system defaults but be over ridable at the project level.. You could accomadate this by adding a new GUI feature at the Project/properties dialog. Add a new ‘capabilities’ tab to this form. In this tab the user could choose which of a capabilities jar files would be used by the project.

[Riyad Kalla]

davout that’s a really good suggestion… I’ll pass it up the chain and see what management thinks.

Thanks for sending that along.

Out of curiosity what was the conflict between the JARs? I can imagine there would be an API conflict because of the big version difference between Spring 2 (new) and Hibernate 3 (old) but I’m just curious how it manifested itself incase others ran into it and I wanted to help them.

[davout]

In MyEclipse r5.5 it is ‘asm.jar’ .

[Riyad Kalla]

Sorry, what I was asking was what was the result of the conflict? An exception? A program crash? Server error? etc.

[Author]

Posts