m2e development team does not have the need nor the resources to maintain subversion integration.
The code is opensource under EPL [1], so you can fork it at github or some other place, make it everything work and use it. That's the beauty of opensource, after all, you don't have to rely on somebody else to solver your problems. IANAL, but to comply with EPL, I believe you will have to make your changes available. Alternatively, you can always checkout the code on command line and import it as existing maven project. This is what I do in the rare case when I have to deal with subversion. [1] https://github.com/sonatype/m2eclipse-subclipse -- Regards, Igor On 12-02-14 4:58 AM, [email protected] wrote:
Hi, So, I checked out the 1.1 milestone of M2E (1.1.0.20120130-2016, to be precise.) I've been trying to figure out how to use the "Check out Maven projects from SCM" feature with Subversion. Formerly, this worked for me through the m2e-subclipse SCM connector. However, I'm not seeing it on the m2e marketplace now, and the latest one I could find on the Sonatype site (https://repository.sonatype.org/content/sites/forge-sites/m2eclipse-subclipse/0.13.0/N/0.13.0.201107071330/) refuses to work with M2E 1.1. I can, of course, just check out a plain project and then convert it to Maven, but it was so convenient to be able to do it in one step! Are there any plans to update this feature for 1.1? Is there anything I can do to help? Thanks, -Gleb _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
