You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2018/01/02 22:25:26 UTC
[maven-gpg-plugin] annotated tag maven-gpg-plugin-1.0-alpha-3
updated (df41a43 -> 5d6eb63)
This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a change to annotated tag maven-gpg-plugin-1.0-alpha-3
in repository https://gitbox.apache.org/repos/asf/maven-gpg-plugin.git.
*** WARNING: tag maven-gpg-plugin-1.0-alpha-3 was modified! ***
from df41a43 (tag)
to 5d6eb63 (tag)
tagging 35f65781c620110f52eafb9ed82fa755d6f68889 (commit)
replaces maven-gpg-plugin-1.0-alpha-1
by Hervé Boutemy
on Mon Mar 5 19:03:31 2007 +0000
- Log -----------------------------------------------------------------
maven-gpg-plugin-1.0-alpha-3 reworked after migration from aggregate svn to split git
-----------------------------------------------------------------------
discard 1671295 [maven-scm] copy for tag maven-gpg-plugin-1.0-alpha-3
discard aa89850 Set back to alpha-3 version number
discard 8acc57f Provide a way to "store" passphrase in reactor build.
discard 2665cca More for MGPG-1 * Prefix properties with "gpg." * Add gpg.skip * Add --batch-mode support * Query password once per project (instead of once per artifact)
discard 2d62c68 MGPG-1, MGPG-2 - remove requirement of password being passed
discard 1a98559 - move plugin-plugin out of 'reporting' for plugins. It's a required part of the site, and does not cause any issues with the reactor or site generation - update to snapshots
discard a05b4b6 o put the license header in there
discard 13a2960 o updating to latest released parent
discard 37b5bbe o fixing use with classifiers and make thigns works like WARs and RARs
discard 2d347ce [maven-release-plugin] prepare for next development iteration
discard e1403da [maven-release-plugin] prepare release maven-gpg-plugin-1.0-alpha-1
discard b95ac04 o Ignore IDEA files.
discard 8eaeab2 o Set issue management to MNG until the plugin gets its own project in JIRA.
discard 0dc32be o Use the normal Maven plugin menu structure. o Add example, FAQ and index pages.
discard f17657a o Adjust whitespace.
discard 8adab5a o Remove non-gpg related info. o Update configuration example so that it uses the maven-gpg-plugin.
discard 34ba165 o Add prerequisites. o Remove url, which is inherited.
discard 9fff2d8 o Add license.
discard de18621 o Fix typos.
discard e386483 o don't sign the POM then change the name, change the name of the file first and then sign or you will end up with a bad signnature. Thanks to Bernd Bohmann.
discard 088a761 o some hacks to make all the signatures come out directory, this case doesn't seem to be easily handled where you just want to add some extension to the existing artifact like a signature.
discard 7094a74 o just run in the verify phase
discard 71d3707 Don't generate signature on artifact when the project is a pom
discard 3510f73 o sign project artifact o sign POM o sign all attached artifacts
discard a0bfe3a o little gpg signing mojo
add 671661b o little gpg signing mojo
add 3248dd3 o sign project artifact o sign POM o sign all attached artifacts
add af83c42 Don't generate signature on artifact when the project is a pom
add 2cc24fe o just run in the verify phase
add 3344e28 o some hacks to make all the signatures come out directory, this case doesn't seem to be easily handled where you just want to add some extension to the existing artifact like a signature.
add 2bce821 o don't sign the POM then change the name, change the name of the file first and then sign or you will end up with a bad signnature. Thanks to Bernd Bohmann.
add 9ab1ded o Fix typos.
add b930d2f o Add license.
add faea11d o Add prerequisites. o Remove url, which is inherited.
add cf91680 o Remove non-gpg related info. o Update configuration example so that it uses the maven-gpg-plugin.
add aa1865b o Adjust whitespace.
add ea621df o Use the normal Maven plugin menu structure. o Add example, FAQ and index pages.
add ae3136a o Set issue management to MNG until the plugin gets its own project in JIRA.
add 53c1d9d [maven-release-plugin] prepare release maven-gpg-plugin-1.0-alpha-1
add 8404257 [maven-release-plugin] prepare for next development iteration
add 75a9d55 o fixing use with classifiers and make thigns works like WARs and RARs
add fbd4684 o updating to latest released parent
add a0e04cf o put the license header in there
add f09ef2b - move plugin-plugin out of 'reporting' for plugins. It's a required part of the site, and does not cause any issues with the reactor or site generation - update to snapshots
add 2119551 MGPG-1, MGPG-2 - remove requirement of password being passed
add 1a8c8e2 More for MGPG-1 * Prefix properties with "gpg." * Add gpg.skip * Add --batch-mode support * Query password once per project (instead of once per artifact)
add 738137d Provide a way to "store" passphrase in reactor build.
add c88a5cb Set back to alpha-3 version number
add 5c0bacc Consume any garbage on System.in before asking for the passphrase
add 35f6578 [maven-release-plugin] prepare release maven-gpg-plugin-1.0-alpha-3
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
annotated tag are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (df41a43)
\
N -- N -- N refs/tags/maven-gpg-plugin-1.0-alpha-3 (5d6eb63)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
['"commits@maven.apache.org" <co...@maven.apache.org>'].