commit | 036dfe005c64a3f881f493806e854ead033c563d | [log] [tgz] |
---|---|---|
author | Tamas Cservenak <tamas@cservenak.net> | Fri Mar 08 09:02:38 2024 +0100 |
committer | GitHub <noreply@github.com> | Fri Mar 08 09:02:38 2024 +0100 |
tree | 5135138543e58b9734915ad50a330045fb4defbc | |
parent | 0771b610492f0818c38d137f771182f51ff28f98 [diff] |
[MGPG-105] [MGPG-108] Make plugin backward compat and update site and doco (#77) Document the latest changes. But also implement Java changes related to agent usage and back compat. Now we distinguish really (and option is un-deprecated): * `useAgent` * `interactive` Means to provide secret needed for signing: |flag|agent pinentry|agent cached|env variable| |---|---|---|---| |`useAgent && interactive` | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | |`useAgent && !interactive` | :x: | :heavy_check_mark: | :heavy_check_mark: | |`!useAgent && interactive` | :x: | :x: | :heavy_check_mark: | |`!useAgent && !interactive` | :x: | :x: | :heavy_check_mark: | Finally, `!bestPractices` provides existing "pass in passphrase as property" mode as well. As first really means "can we talk to the agent" and second means "can agent pop up pinentry dialogue" for both signers. In fact, this was the case already in `GpgSigner`, but `BcSigner` conflated the two. As it turns out, `gpg-agent` also supports "non interactive" password caching that now both signers make use of. --- https://issues.apache.org/jira/browse/MGPG-108 https://issues.apache.org/jira/browse/MGPG-105
You have found a bug or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:
git diff --check
before committing.[MGPG-XXX] - Subject of the JIRA Ticket Optional supplemental description.
mvn -Prun-its verify
to assure nothing else was accidentally broken.If you plan to contribute on a regular basis, please consider filing a contributor license agreement.
For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA. In this case, it is appropriate to start the first line of a commit with ‘(doc)’ instead of a ticket number.