Hi,
I’m trying to switch from plain Eclipse Kepler to MyEclipse Pro; I’m having some issues deploying legacy WTP spring+maven based project on the Tomcat server. I have completed successfully the migration of the old projects.
I’m still able open the workspace with the old kepler installation, and run the server with no problems; but when I try to deploy the same project to myeclipse embedded tomcat, then it fails on startup with some spring errors (Caused by: org.hibernate.DuplicateMappingException: duplicate import) which are not there when I start the application on plain kepler (for sake of completeness, the duplicate entities are in different packages, and are not loaded at the same time; they are legacy code which I cannot refactor).
Apparently, myeclipse is loading the spring context differently from WTP, and I would like to understand and control the way it bootstraps the spring context; I need to interoperate with NON-myeclipse projects transparently, but would like to keep the benefit of running my eclipse.
Can somebody help?