Some documentation on how this is done for maven-bundle-plugin is available at [1] leveraging the maven-scm-publish-plugin [3]. The pom.xml shows what needs to be configured[2]. In contrast to the Maven Bundle Plugin we should use dedicated URLs per version of each plugin.
Konrad [1] - http://felix.apache.org/documentation/development/release-management-nexus.html#stage-the-generated-documentation [2] - https://github.com/apache/felix/blob/trunk/tools/maven-bundle-plugin/pom.xml#L102 [3] - http://maven.apache.org/plugins/maven-scm-publish-plugin/ > Am 28.09.2016 um 23:28 schrieb Stefan Seifert <[email protected]>: > > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > sling provides a couple of maven plugins, but does not provide a detailed > documentation about their goals and properties at [1]. > > such a documentation can be generated easily by using the maven site for the > plugin project. the only question is: how should it be published and > integrated in the maven site? > > it would be sufficient to link to it from the maven site, it does not > necessarily have to be "fully integrated" in the layout of the sling docs > pages. > > the documentation for the different releases of maven plugins should be > available in parallel. > > one option would be to generate the site and include it in the sling site > svn. this is not very elegant and will bloat the site svn, and it is bad > practice to check in generated markup, but it would work. but it is a > manually step one to execute on each release of a maven plugin. > > next step would be creating a JIRA ticket for this. > > stefan > > [1] http://sling.apache.org/ > >
