SCM-948 - Make limit parameter work for svnexe and gitexe changelog goal

[cquoss]

No description provided.

[eolivelli]

Can you please explain more your patch?

[cquoss]

Happily. The old PR was better documented but got erased after resetting hard to upstream master and force pushing.
At our company we use a customized version of maven-release that talks in some added phases with our jira.
To be more precise we extract in one phase the current jira issue related with this maven project from the latest scm commit comment.
To not have the scm provider always drill down through the complete log history i also customized maven-scm in our nexus repository to only return the latest log entry by making the limit parameter functional for the changelog goal for the two providers we are interested in (gitexe and svnexe).
My patch here may not be perfect but with all the abstraction and the already deprecated methods i made two attempts in the past (the first inventing new methods and instantly deprecating them, the second removing all deprecation from the code and directly go through request -> parameters to command line creation).
Both have been rejected so now this is my third attempt doing this by overriding the executeCommand method for these two providers mentioned.

[cquoss]

Another thing: Travis CI builds for jdk 7 and 8 have errors. To me it looks like jdk 7 and 8 are not available. Is some on it to fix the config on this?

[michael-o]

This <p> isn't necessary.

[michael-o]

Note: The order how those options are processed differ between Subversion and Git. This is bad for consistency, but not your fault I do not expect you to fix that. The change looks fine to me.