You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ss...@apache.org on 2017/12/08 12:20:08 UTC
[sling-site] 01/03: update steps to release a maven plugin site -
do it manually instead of using maven-scm-publish-plugin which does not
seem to work with our git site setup
This is an automated email from the ASF dual-hosted git repository.
sseifert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
commit a400c6e00b7e18e0849786aafbf2d556f344aacb
Author: sseifert <ss...@pro-vision.de>
AuthorDate: Fri Dec 8 13:08:41 2017 +0100
update steps to release a maven plugin site - do it manually instead of using maven-scm-publish-plugin which does not seem to work with our git site setup
---
.../documentation/development/release-management.md | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md
index 9aaef65..c8da6a8 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -395,27 +395,24 @@ To publish the plugin documentation execute the following steps after the releas
1. Checkout the release tag of the released plugin (or reset your workspace)
-2. Build and stage the maven site of the plugin. Note that this *commits* the generated content to the components folder mentioned below.
+2. Build and stage the maven site of the plugin locally.
- $ mvn clean site:site site:stage scm-publish:publish-scm
+ $ mvn clean site:site site:stage
3. Checkout the Sling website and navigate to the 'components' directory
$ git clone https://github.com/apache/sling-site.git
- $ cd sling-site/src/main/jbake/assets/components/
-4. SVN-rename the generated documenation that the site plugin commited to `<plugin-name>-archives/<plugin-name>-LATEST` to `<plugin-name>-archives/<plugin-name>-<version>`
-
-5. SVN-remove the existing folder `<plugin-name>` and SVN-copy the folder `<plugin-name>-archives/<plugin-name>-<version>` to `<plugin-name>`
+4. Replace the content of the existing folder `src/main/jbake/assets/components/<plugin-name>` with the generated maven site from `target/staging`
-6. Commit the changes.
+5. Create a new folder `src/main/jbake/assets/components/<plugin-name>-archives/<plugin-name>-<version>` and copy the generated maven site there as well
+
+6. Commit the changes
7. Publish the Sling site to production
8. 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).
-
## Appendix C: Deploy bundles on the Sling OBR (obsolete)
*Update November 2016: We do now longer maintain the Sling OBR for new releases.*
--
To stop receiving notification emails like this one, please contact
"commits@sling.apache.org" <co...@sling.apache.org>.