You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bd...@apache.org on 2017/03/10 07:54:35 UTC
svn commit: r1786296 -
/sling/site/trunk/content/documentation/development/release-management.mdtext
Author: bdelacretaz
Date: Fri Mar 10 07:54:35 2017
New Revision: 1786296
URL: http://svn.apache.org/viewvc?rev=1786296&view=rev
Log:
Tweaks to release management page
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=1786296&r1=1786295&r2=1786296&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Fri Mar 10 07:54:35 2017
@@ -432,7 +432,7 @@ To update the OBR you may use the Apache
## Appendix D: Deploy Maven plugin documentation (if applicable)
-When releasing a Maven plugin, the Maven-generated documentation published under http://sling.apache.org/components/ needs
+When releasing a Maven plugin, the Maven-generated documentation published under [http://sling.apache.org/components/](http://sling.apache.org/components/) needs
to be updated.
This is currently supported for:
@@ -453,12 +453,12 @@ To publish the plugin documentation exec
$ svn checkout https://svn.apache.org/repos/infra/websites/production/sling/content/components
-4. svn move the `<plugin-name>` subfolder there under <plugin-name>-archives/<plugin-name>-<version>`, if not present yet
+4. svn move the `<plugin-name>` subfolder there under `<plugin-name>-archives/<plugin-name>-<version>`, if not present yet
-5. svn import the documentation generated by Maven site:site as `<plugin-name>' there.
+5. svn import the documentation generated by Maven site:site as `<plugin-name>` there.
6. Commit the changes.
7. Check the results at [http://sling.apache.org/components/](http://sling.apache.org/components/)
-For background information about this process see [the Maven components reference documentation](http://maven.apache.org/developers/website/deploy-component-reference-documentation.html).
+For background information about this process see the [Maven components reference documentation](http://maven.apache.org/developers/website/deploy-component-reference-documentation.html).