cquoss edited a comment on pull request #110:
URL: https://github.com/apache/maven-scm/pull/110#issuecomment-883621726
At the moment we use a customized version of maven-scm as well containing my
first approach to make the limit parameter work by using deprecated methods.
That was not in your favor as well, with my second approach i overstepped quite
a bit. So OK.
This is the relevant code used in our customized release phase (we called it
scm-extract-comment):
ScmRepository repository = configureScmRepository( configurator, descriptor,
environment );
ScmProvider provider = getProvider( configurator, repository );
ScmRevision headRevision = new ScmRevision( "HEAD" );
ChangeLogScmResult logResult;
try
{
ChangeLogScmRequest logRequest = new ChangeLogScmRequest( repository,
fileSet );
logRequest.setLimit( 1 );
logRequest.setRevision( headRevision );
logResult = provider.changeLog( logRequest );
...
As you can see we hand down a log request containing the limit option of 1,
since we are only interested in the latest log entry.
So my solution should contain amendments to hand over this log request to
the svn and git command line, without using the deprecated methods. Correct?
Just trying to make sure not to burn more useless hours on this.
--
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]
