Child pages
  • Sling module descriptor
Skip to end of metadata
Go to start of metadata

Rationale

We have a number of automated processes which make use of the Git repositories as a source of truth:

  • generating a default.xml manifest for repo checkout
  • generating Jenkins jobs

However, we often have the need to override some of the logic on a per-module basis:

  • building a project with multiple JDKs
  • including certain modules in repo groups or creating special profiles for them

In the future, we may look into other automation, such as:

  • generating a Jenkinsfile per each module
  • automatically maintaining a README.md which points to documentation URLs or the build Job

Therefore it is proposed to allow the existence of a Sling module descriptor file in the root of each Git repository. If no descriptor exists, the module is processed by various tools in the default manner. If it exists, the tools must inspect it for custom settings and apply them.

Structure

The module file will be named .sling-module.xml . It is a "dotfile" as it is not usually touched during regular development. The XML format easy consumption from various tools and , compared to JSON, allows defining comments.

Rather than listing a specification, a full example is provided below:

sling-module.xml example
  • No labels