[
https://issues.apache.org/jira/browse/LUCENE-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125897#comment-14125897
]
Uwe Schindler commented on LUCENE-5594:
---------------------------------------
Hi,
I am working on this. I will put up a patch soon.
My work includes not calling the svn executable at all, instead we use svnkit
to revision numbers or checkout the src folder.
This speeds up the build, because we do not need to fork a process all the
time, which is expensive on windows and on freebsd jenkins (because we fork
Java). Using svnkit to do this and saving the revision number in a property
helps. It makes also Jenkins builds more easy to configure, because you do not
depend on local svn installations (e.g. Jenkins checks out with different
version than locally installed). This is an issue on Policeman enkins and
FreeBSD Jenkins.
> don't call 'svnversion' over and over in the build
> --------------------------------------------------
>
> Key: LUCENE-5594
> URL: https://issues.apache.org/jira/browse/LUCENE-5594
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
>
> Some ant tasks (at least release packaging, i dunno what else), call
> svnversion over and over and over for each module in the build. can we just
> do this one time instead?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
