[
https://issues.apache.org/jira/browse/LUCENE-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2267:
----------------------------------
Attachment: LUCENE-2267.patch
Patch with a heavy improved version of solrs macros, I changed:
- For security reasons, the password is not passed through command line (you
can see it with "ps \-ef" !!!). Also "\-\-passphrase" does not work with newer
2.x versions of gpg. The correct way is the same as in Mike McCandless Python
script to pass "\-\-passphrase-fd 0" (then it read the passphrase from stdin),
piping in the password using the "inputstring" task attribute of ant.
- added "\-\-batch" parameter to gpg. Without, in GUI environments it ignores
the passed-in password and uses gpg-agent
- no manual signing of every file, it uses the <apply> ant task that starts a
process for every file in a fileset and also supplies a source -> desfilename
mapping (which appends ".asc")
- add "\-\-default-key" with a default value of "CODE SIGNING KEY", you can
override with "\-Dgpg.key=YourHexKeyOrEmail"
The only problem is that <appy> does not print the command lines or some
filelist. You only get a message at the end that "applied 'gpg' to x files",
which is fine.
Usage:
{code}
ant sign-artifacts -Dgpg.exe=/path/to/gpg -Dgpg.key=YourHexKeyOrEmail
-Dgpg.passphrase=12345
{code}
All parameters are optional, defaults are:
{code}
gpg.exe = "gpg"
gpg.key = "CODE SIGNING KEY"
gpg.passphrase = <none>, if not given, you are asked to input
{code}
> Add solr's artifact signing scripts into lucene's build.xml/common-build.xml
> ----------------------------------------------------------------------------
>
> Key: LUCENE-2267
> URL: https://issues.apache.org/jira/browse/LUCENE-2267
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 2.9.2, 3.0.1
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 3.1
>
> Attachments: LUCENE-2267.patch
>
>
> Solr has nice artifact signing scripts in its common-build.xml and build.xml.
> For me as release manager of 3.0 it would have be good to have them also when
> building lucene artifacts. I will investigate how to add them to src
> artifacts and maven artifacts
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
