[
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075046#comment-15075046
]
Uwe Schindler edited comment on LUCENE-6938 at 12/30/15 2:05 PM:
-----------------------------------------------------------------
Hi,
the current build relies on SVN at 3 places:
- "ant check-svn-working-copy" as part of "ant validate" and "ant precommit".
This is not critical and can be fixed later. The task gets a no-op if executed
from non-svn, so we can fix later, no need to hurry. I will take care of that
and prepare patch to use "jgit" for similar checks
(https://www.eclipse.org/jgit/). I'll open separate issue if needed.
- Currently we call "svnversion" and place output inside all JAR files. I would
like to remove this completely. We can of course add the commit hash, but
somehow this makes no sense, as the commit hashes cannot be sorted and don't
have a "version like" character. So +1 to remove "svnversion" calls during JAR
building and just place version number in JAR files, but no revision/hash.
- The source tar gz/zip files use svn export. We have to fix this, otherwise we
cannot release and test.
Jenkins builds need to be updated, but thats easy. Policeman is already
prepared to do git checkouts (using jgit, see above).
was (Author: thetaphi):
Hi,
the current build relies on SVN at 2 places:
- "ant check-svn-working-copy" as part of "ant validate" and "ant precommit".
This is not critical and can be fixed later. The task gets a no-op if executed
from non-svn, so we can fix later, no need to hurry. I will take care of that
and prepare patch to use "jgit" for similar checks
(https://www.eclipse.org/jgit/). I'll open separate issue if needed.
- Currently we call "svnversion" and place output inside all JAR files. I would
like to remove this completely. We can of course add the commit hash, but
somehow this makes no sense, as the commit hashes cannot be sorted and don't
have a "version like" character. So +1 to remove "svnversion" calls during JAR
building and just place version number in JAR files, but no revision/hash.
- The source tar gz/zip files use svn export. We have to fix this, otherwise we
cannot release and test.
- Jenkins builds need to be updated, but thats easy. Policeman is already
prepared to do git checkouts (using jgit, see above).
> Convert build to work with Git rather than SVN.
> -----------------------------------------------
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Mark Miller
> Assignee: Mark Miller
>
> We assume an SVN checkout in parts of our build and will need to move to
> assuming a Git checkout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
