o exclude fml files in copy

o easier use of classic that always works


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@115188 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
brett
2004-05-05 07:38:31 +00:00
parent 0a02de2005
commit 6f5b5a1b9f
5 changed files with 5 additions and 2 deletions

View File

@@ -583,6 +583,7 @@
<copy todir="${maven.docs.dest}" filtering="no">
<fileset dir="${maven.docs.src}">
<exclude name="**/*.xml"/>
<exclude name="**/*.fml"/>
<exclude name="**/CVS/*"/>
<exclude name="stylesheets/*"/>
</fileset>

View File

@@ -25,6 +25,7 @@ maven.xdoc.includeProjectDocumentation = yes
maven.xdoc.crumb.separator=|
maven.xdoc.theme.url=
maven.xdoc.theme=theme
# Location where the artifacts are distributed. This property is optional.
# If it is not defined, then the Download report will not be added to the

View File

@@ -60,7 +60,7 @@
@import url("${maven.xdoc.theme.url}");
]]></j:if>
<j:if test="${empty(themeUrl)}"><![CDATA[
@import url("${relativePath}/style/maven-theme.css");
@import url("${relativePath}/style/maven-${maven.xdoc.theme}.css");
]]></j:if>
<j:if test="${projectCssFile.exists()}"><![CDATA[
@import url("${relativePath}/style/project.css");

View File

@@ -26,6 +26,7 @@
</properties>
<body>
<release version="1.7-SNAPSHOT" date="in CVS">
<action dev="brett" type="fix">Exclude .fml files from copy to target directory</action>
<action dev="brett" type="add">Add a "classic" theme CSS</action>
<action dev="vmassol" type="add">
Added new download report along with a new link in the Maven

View File

@@ -26,7 +26,7 @@
<question>How can I get the "classic" (Maven 1.0 RC1 and below) theme on my site?</question>
<answer>
You can switch to the classic CSS by setting
<source>maven.xdoc.theme.url=./style/maven-classic.css</source>
<source>maven.xdoc.theme=classic</source>
</answer>
</faq>