Oct 11th, 2012, 03:08 AM
How do I prevent Maven -> Update Project... from adding the Spring project nature?
We have a Maven multi-module project with a very bulky spring configuration. We should refactor the spring config in the foreseeable future, but until we get around to do that, having the Spring project nature enabled on the projects results in an unacceptably slow build.
We have the projects completely in version control (including working .project and .classpath files that only include the java and maven project natures). When importing the projects from SVN or performing Maven -> Update Project, m2e insists on adding the Spring project nature to the .project files. Is there any way we can prevent this from happening?
We are using STS 3.1 with m2e 1.2.0.
Thanks in advance to any who can help!