Author: npeltier
Date: Tue Jul 11 09:17:41 2017
New Revision: 1801579
URL: http://svn.apache.org/viewvc?rev=1801579&view=rev
Log:
Adding instructions in case releaser hit MGPG-59
Modified:
sling/site/trunk/content/documentation/development/release-management.mdtext
Modified:
sling/site/trunk/content/documentation/development/release-management.mdtext
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/release-management.mdtext?rev=1801579&r1=1801578&r2=1801579&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/development/release-management.mdtext
(original)
+++
sling/site/trunk/content/documentation/development/release-management.mdtext
Tue Jul 11 09:17:41 2017
@@ -66,6 +66,7 @@ First prepare your POMs for release:
...
* If you experience an error during deployment like a HTTP 401 check your
settings for the required server entries as outlined in the *Prerequisites*
+ * Depending on the OS & the gpg version you have, you might hit
https://issues.apache.org/jira/browse/MGPG-59, in which case you need, before
maven command, to run `gpg --use-agent --armor --detach-sign --output $(mktemp)
pom.xml`
* Make sure the generated artifacts respect the Apache release
[rules](http://www.apache.org/dev/release.html): NOTICE and LICENSE files
should be present in the META-INF directory within the jar. For \-sources
artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3
which is broken. The recommended version at this time is 2.0.4
* You should verify the deployment under the
[snapshot](https://repository.apache.org/content/groups/snapshots/org/apache/sling)
repository on Apache
