Instructions

Follow these steps to include commons-skin in a component's Maven 2 build.

  • Include commons-skin in the src/site/site.xml file of your component:
    <project name="...">
      ...
      <skin>
        <groupId>org.apache.commons</groupId>
        <artifactId>commons-skin</artifactId>
        <version>1.0</version>
      </skin>
      ...
    </project>
    

  • If you have both a Maven 1 and a Maven 2 site build for your component, you need to exclude the Maven 1 navigation.xml file from the Maven 2. This is done with a configuration snippet in the file pom.xml:
    <project ...>
      ...
      <reporting>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-site-plugin</artifactId>
            <configuration>
              <moduleExcludes>
                <xdoc>navigation.xml</xdoc>
              </moduleExcludes>
            </configuration>
          </plugin>
        </plugins>
      </reporting>
      ...
    </project>
    

  • A final note for sandbox components. The site might not look as it should if you have checked out your component as a part of /commons/trunks-sandbox. This is because trunks-sandbox has some build-in stylesheet customizations that might interfere with the stylesheet definitions in the skin. The solution is to check out the component on its own. This problem will be fixed if/when commons-skin is released.
  • No labels