You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Apache Wiki <wi...@apache.org> on 2006/12/27 21:53:24 UTC
[Jakarta-commons Wiki] Update of "UsingCommonsSkin" by DennisLundberg
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.
The following page has been changed by DennisLundberg:
http://wiki.apache.org/jakarta-commons/UsingCommonsSkin
The comment on the change is:
Add instruction on how to use commons-skin
New page:
== 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-SNAPSHOT</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 {{{/jakarta/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.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org