cquoss edited a comment on pull request #119: URL: https://github.com/apache/maven-scm/pull/119#issuecomment-886156115
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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
