So for my project I am in need of Subclipse 1.8.x. This has been well and good, but the maven SCM handler for subclipse is only compatible with Subclipse 1.6.x. I like this plugin because it automatically loads modules (and detects them), so you can store your poms in a hierarchical fashion in svn. ( parent / module + module / module) etc. and checking out a multi-module maven project with the handler only requires one check out.
Since I cannot count on that working, how should I store multi-module maven projects in svn? Store them flat-level (Eclipse-style) in svn, check them out one at a time with help of m2e – the parent, and then each module individually? would that play nice with subclipse? I don't want to store auto-generated files, just resources, poms, and source files.
There is also this: https://github.com/sonatype/m2eclipse-subclipse/pull/4
Apparently that is a solution, and that enables the svn protocol for checking out multi-maven projects via scm (even with Subclipse 1.8.x). However, when I put it in my dropins folder in eclipse, I stil don't see the connector?
The dropin structure can be seen below, should work according to what I've read, but I am still unable to find the scm handler even after restarting eclipse. I want to begin development but this is holding us back.
http://i42.tinypic.com/2465aas.jpg
Am using m2e version: 1.1.0.20120130-2016.
Thank you,
Best Answer
The lack of response on this issue from the m2e people has been disappointing. Thankfully the guys from Subclipse have recently come to our rescue. They have forked the project, applied the patch and created an update site which publishes the new version. In short, Maven SCM Handler for Subclipse is finally compliant with Subclipse 1.8.x
Just make sure you use this update site to install in the future and all is well again in the universe. :o)
http://subclipse.tigris.org/m2eclipse/1.0
UPDATE 10/03/2014: Similar problem when upgrading to Subclipse 1.10.x, see this post