[sling-site] branch master updated: Get rid of failing sling:stage goal (#96)

[kw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 42e13cf72 Get rid of failing sling:stage goal (#96)
42e13cf72 is described below

commit 42e13cf729f8899d90ba132dd85fb99a1aaa0e23
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Mon Aug 15 08:59:22 2022 +0200

    Get rid of failing sling:stage goal (#96)
    
    sling:stage is only useful for multi-module sites and requires a proper URL to be set in the distribution management
    related discussion in https://lists.apache.org/thread/yw31s9m5dx7ky99k91yzl2tghgo7k2b8
---
 .../documentation/development/release-management.md      | 16 ++++------------
 1 file changed, 4 insertions(+), 12 deletions(-)

diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md
index 51c982958..640e6c3a2 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -419,27 +419,19 @@ Assuming you are using a \*nix system with a working OpenSSH, GnuPG, and bash yo
 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:
-
-* `sling-maven-plugin`
-* `htl-maven-plugin`
-* `jspc-maven-plugin`
-* `slingstart-maven-plugin`
-* `slingfeature-maven-plugin`
-
 To publish the plugin documentation execute the following steps after the release:
 
 1. Checkout the release tag of the released plugin (or reset your workspace)
 
-2. Build and stage the maven site of the plugin locally.
+2. Build the Maven site of the plugin locally.
    
-        $ mvn clean site:site site:stage
+        $ mvn clean site:site
 
-3. Checkout the Sling website and navigate to the 'components' directory
+3. Checkout the Sling website
 
         $ git clone https://github.com/apache/sling-site.git
 
-4. Replace the content of the existing folder `src/main/jbake/assets/components/<plugin-name>` with the generated maven site from `target/staging`
+4. Replace the content of the existing folder `src/main/jbake/assets/components/<plugin-name>` with the generated Maven site from `target/site`
 
 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