Even with SVN command-line tools installed (e.g. I used TortoiseSVN), the maven release plugin then dies doing the release:prepare goal. Looks like it is looking for the maven CLI executable as well, where again Eclipse is using its internal maven plugin. This results in:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project idfc-proguard-maven-plugin: Failed to invoke Maven build. Error configuring command-line. Reason: Maven executable not found at: D:\dev\workspace\IDFC ProGuard Maven Plugin\EMBEDDED\bin\mvn.bat -> [Help 1]
Has anyone found a configuration technique to make these plugins run properly from within Eclipse using the installed Eclipse plugins, or does using the maven release plugin basically require the installation of SCM and Maven CLI outside of Eclipse?
From: Richard Sand [mailto:rsand@xxxxxxxxxxxxxx]
Sent: Wednesday, July 17, 2013 2:45 PM
To: 'Maven Integration for Eclipse users mailing list'
Subject: RE: [m2e-users] can m2e use subclipse or other eclipse svn plugin?
I have subclipse installed and it works fine, as does m2e – when I do “Run as Maven” and execute the goal “release:prepare”, the release plugin executes svn to check in the latest project and tag it at the release level. But it’s looking for svn on the system path. I’m just wondering if anyone has figured out how to make this goal execute without installing a separate command-line svn executable.
-Richard
From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] On Behalf Of Matthew Piggott
Sent: Wednesday, July 17, 2013 2:22 PM
To: Maven Integration for Eclipse users mailing list
Subject: Re: [m2e-users] can m2e use subclipse or other eclipse svn plugin?
There are subclipse and subversive connectors for checking out projects, and they should use whatever subclipse/subvsersive are configured to use. Neither are part of the Eclipse m2e project however.