Hi Stefan,
thanks a lot for your efforts.
Can we also add a hint on how to deploy a SNAPSHOT site (e.g. for others to
review?)
Thanks,
Konrad
> On 10 Mar 2017, at 01:25, Stefan Seifert <sseif...@pro-vision.de> wrote:
>
> for a long time we manually maintained documentation of our maven plugins in
> the sling site, which is tedious and error-prone.
>
> inspired by the process used by the felix maven-bundle-plugin i've set up the
> same for the three most important sling plugins:
> - maven-sling-plugin [1]
> - htl-maven-plugin [2]
> - slingstart-maven-plugin [3]
>
> i've also updated the release management documentation [4] - everyone
> publishing a new release of a maven plugin should update the site as well.
> although it involves some manual steps it's quite easy and straightforward.
>
> the new section /components [5] on the site is excluded from the normal site
> publishing process and is only updated when publishing a new maven site (same
> as in felix). the folder also contains the archived documentations of the old
> plugins. whe might use the same concept for publishing the Sling API in the
> future as well. the concept is taken from [6].
>
> stefan
>
> [1] http://sling.apache.org/components/maven-sling-plugin/plugin-info.html
> [2] http://sling.apache.org/components/htl-maven-plugin/plugin-info.html
> [3]
> http://sling.apache.org/components/slingstart-maven-plugin/plugin-info.html
> [4]
> http://sling.apache.org/documentation/development/release-management.html#appendix-d-deploy-maven-plugin-documentation
> [5] http://sling.apache.org/components
> [6]
> http://maven.apache.org/developers/website/deploy-component-reference-documentation.html
>
>
