You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sl...@apache.org on 2026/08/06 17:11:30 UTC
(maven-clean-plugin) branch maven-clean-plugin-3.x updated (a5b6613 -> 1b5d73a)
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch maven-clean-plugin-3.x
in repository https://gitbox.apache.org/repos/asf/maven-clean-plugin.git
from a5b6613 Align PR template (#327)
new c3f2943 Rename the site documents ahead of converting them
new 1b5d73a Port the site documentation from APT to Markdown
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../apt/examples/delete_additional_files.apt.vm | 78 ------------------
src/site/apt/examples/ignoring-errors.apt.vm | 51 ------------
src/site/apt/examples/skipping-clean.apt.vm | 51 ------------
src/site/apt/index.apt.vm | 75 ------------------
src/site/apt/usage.apt.vm | 92 ----------------------
.../examples/delete_additional_files.md.vm | 65 +++++++++++++++
.../site/markdown/examples/ignoring-errors.md.vm | 38 +++++----
.../site/markdown/examples/skipping-clean.md.vm | 38 +++++----
src/site/markdown/index.md | 42 ++++++++++
src/site/markdown/usage.md.vm | 74 +++++++++++++++++
10 files changed, 229 insertions(+), 375 deletions(-)
delete mode 100644 src/site/apt/examples/delete_additional_files.apt.vm
delete mode 100644 src/site/apt/examples/ignoring-errors.apt.vm
delete mode 100644 src/site/apt/examples/skipping-clean.apt.vm
delete mode 100644 src/site/apt/index.apt.vm
delete mode 100644 src/site/apt/usage.apt.vm
create mode 100644 src/site/markdown/examples/delete_additional_files.md.vm
copy AGENTS.md => src/site/markdown/examples/ignoring-errors.md.vm (56%)
copy AGENTS.md => src/site/markdown/examples/skipping-clean.md.vm (58%)
create mode 100644 src/site/markdown/index.md
create mode 100644 src/site/markdown/usage.md.vm
(maven-clean-plugin) 02/02: Port the site documentation from APT to Markdown
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch maven-clean-plugin-3.x
in repository https://gitbox.apache.org/repos/asf/maven-clean-plugin.git
commit 1b5d73ae5a203a5ff0a785226712e08c9f546e88
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Thu Aug 6 13:52:57 2026 +0200
Port the site documentation from APT to Markdown
6 page(s) converted with doxia-converter and then cleaned up by hand:
- <<<code>>> becomes backticks, <<bold>> becomes **bold**, {{{url}text}}
becomes [text](url)
- the ASF license header becomes a single block HTML comment
- a page whose only Velocity reference was ${project.name} is now a plain
.md with the title spelled out
- a page that keeps a reference stays a .vm. Velocity reads ## as a line
comment and would silently swallow every ATX heading below level one, so
subsections use setext underlines and anything deeper is wrapped in
#[[ ... ]]#
- references APT rendered literally are escaped, so they do not resolve
Verified by building the site before and after and comparing every
generated page: the visible text and the link targets are unchanged apart
from <b>/<i> becoming <strong>/<em> and quotes in prose picking up the
Markdown module's typographic substitution.
---
.../examples/delete_additional_files.md.vm | 69 +++++++---------
src/site/markdown/examples/ignoring-errors.md.vm | 55 ++++++-------
src/site/markdown/examples/skipping-clean.md.vm | 55 ++++++-------
src/site/markdown/index.md | 93 +++++++---------------
src/site/markdown/usage.md.vm | 88 ++++++++------------
5 files changed, 139 insertions(+), 221 deletions(-)
diff --git a/src/site/markdown/examples/delete_additional_files.md.vm b/src/site/markdown/examples/delete_additional_files.md.vm
index 0fa768c..8ed5177 100644
--- a/src/site/markdown/examples/delete_additional_files.md.vm
+++ b/src/site/markdown/examples/delete_additional_files.md.vm
@@ -1,38 +1,27 @@
- ------
- Delete Additional Files Not Exposed to Maven
- ------
- Mike Perham
- <mp...@apache.org>
- ------
- 2007-11-14
- ------
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
+http://www.apache.org/licenses/LICENSE-2.0
-~~ NOTE: For help with the syntax of this file, see:
-~~ http://maven.apache.org/doxia/references/apt-format.html
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
-Delete Additional Files Not Exposed to Maven
+# Delete Additional Files Not Exposed to Maven
- The Maven Clean Plugin will delete the <<<target>>> directory by default. You may configure
- it to delete additional directories and files. The following example shows how:
+The Maven Clean Plugin will delete the `target` directory by default. You may configure it to delete additional directories and files. The following example shows how:
-+--------
+```xml
<build>
[...]
<plugin>
@@ -57,22 +46,20 @@ Delete Additional Files Not Exposed to Maven
</plugin>
[...]
</build>
-+---------
+```
- <<Note:>> The <<<directory>>> in the <<<fileset>>> is a relative path inside a project, in other words,
+**Note:** The `directory` in the `fileset` is a relative path inside a project, in other words,
-+--------
+```xml
<directory>some/relative/path</directory>
-+--------
+```
- is equivalent to:
+is equivalent to:
-+--------
+```xml
<directory>${project.basedir}/some/relative/path</directory>
-+--------
+```
- You could also define file set rules in a parent POM. In this case, the clean plugin adds the subproject
- basedir to the defined relative path.
+You could also define file set rules in a parent POM. In this case, the clean plugin adds the subproject basedir to the defined relative path.
- <<Note:>> The <<<fast>>> delete method will not work for any <<<fileset>>> which defines any <<<includes>>>
- or <<<excludes>>>, or sets <<<followSymlinks>>> to <<<false>>>, or sets <<<useDefaultExcludes>>> to <<<true>>>.
\ No newline at end of file
+**Note:** The `fast` delete method will not work for any `fileset` which defines any `includes` or `excludes`, or sets `followSymlinks` to `false`, or sets `useDefaultExcludes` to `true`.
diff --git a/src/site/markdown/examples/ignoring-errors.md.vm b/src/site/markdown/examples/ignoring-errors.md.vm
index 4751b4b..b86826c 100644
--- a/src/site/markdown/examples/ignoring-errors.md.vm
+++ b/src/site/markdown/examples/ignoring-errors.md.vm
@@ -1,36 +1,27 @@
- ------
- Ignoring Clean Errors
- ------
- Vincent Siveton
- ------
- 2007-11-13
- ------
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
+http://www.apache.org/licenses/LICENSE-2.0
-~~ NOTE: For help with the syntax of this file, see:
-~~ http://maven.apache.org/doxia/references/apt-format.html
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
-Ignoring Clean Errors
+# Ignoring Clean Errors
- To ignore errors when running the cleanup for a particular project, set the <<<failOnError>>> property to <<<false>>>.
+To ignore errors when running the cleanup for a particular project, set the `failOnError` property to `false`.
-+--------
+```xml
<build>
[...]
<plugin>
@@ -42,10 +33,10 @@ Ignoring Clean Errors
</plugin>
[...]
</build>
-+---------
+```
- You can also ignore them via command line by executing the following command:
+You can also ignore them via command line by executing the following command:
-+--------
+```shell
mvn clean -Dmaven.clean.failOnError=false
-+---------
+```
diff --git a/src/site/markdown/examples/skipping-clean.md.vm b/src/site/markdown/examples/skipping-clean.md.vm
index 388d023..77a5998 100644
--- a/src/site/markdown/examples/skipping-clean.md.vm
+++ b/src/site/markdown/examples/skipping-clean.md.vm
@@ -1,36 +1,27 @@
- ------
- Skipping Clean
- ------
- Vincent Siveton
- ------
- 2007-11-13
- ------
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
+http://www.apache.org/licenses/LICENSE-2.0
-~~ NOTE: For help with the syntax of this file, see:
-~~ http://maven.apache.org/doxia/references/apt-format.html
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
-Skipping Clean
+# Skipping Clean
- To skip running the cleanup for a particular project, set the <<<skip>>> property to <<<true>>>.
+To skip running the cleanup for a particular project, set the `skip` property to `true`.
-+--------
+```xml
<build>
[...]
<plugin>
@@ -42,10 +33,10 @@ Skipping Clean
</plugin>
[...]
</build>
-+---------
+```
- You can also skip the cleaning via command line by executing the following command:
+You can also skip the cleaning via command line by executing the following command:
-+--------
+```shell
mvn clean -Dmaven.clean.skip=true
-+---------
+```
diff --git a/src/site/markdown/index.md b/src/site/markdown/index.md
index 2f21f03..0f6fad4 100644
--- a/src/site/markdown/index.md
+++ b/src/site/markdown/index.md
@@ -1,75 +1,42 @@
- ------
- Introduction
- ------
- Edwin Punzalan
- ------
- 2013-07-22
- ------
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
+http://www.apache.org/licenses/LICENSE-2.0
-~~ NOTE: For help with the syntax of this file, see:
-~~ http://maven.apache.org/doxia/references/apt-format.html
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
-${project.name}
+# Apache Maven Clean Plugin
+The Clean Plugin is used when you want to remove files generated at build-time in a project's directory.
- The Clean Plugin is used when you want to remove files generated at
- build-time in a project's directory.
+## Goals Overview
-* Goals Overview
+The Clean Plugin only has one goal.
- The Clean Plugin only has one goal.
+- [clean:clean](./clean-mojo.html) attempts to clean a project's working directory of the files that were generated at build-time. By default, it discovers and deletes the directories configured in `project.build.directory`, `project.build.outputDirectory`, `project.build.testOutputDirectory`, and `project.reporting.outputDirectory`.
+## Usage
- * {{{./clean-mojo.html}clean:clean}} attempts to clean a project's working
- directory of the files that were generated at build-time. By default, it
- discovers and deletes the directories configured in
- <<<project.build.directory>>>, <<<project.build.outputDirectory>>>,
- <<<project.build.testOutputDirectory>>>, and
- <<<project.reporting.outputDirectory>>>.
+General instructions on how to use the Clean Plugin can be found on the [usage page](./usage.html). Some more specific use cases are described in the examples given below.
-* Usage
+In case you still have questions regarding the plugin's usage, please have a look at the [FAQ](./faq.html) and feel free to contact the [user mailing list](./mailing-lists.html). The posts to the mailing list are archived and could already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching the [mail archive](./mailing-lists.html).
- General instructions on how to use the Clean Plugin can be found on the {{{./usage.html}usage page}}. Some more
- specific use cases are described in the examples given below.
+If you feel like the plugin is missing a feature or has a defect, you can submit a feature request or bug report in our [issue tracker](./issue-management.html). When creating a new issue, please provide a comprehensive description of your concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason, entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated. Of course, patches are w [...]
- In case you still have questions regarding the plugin's usage, please have a look at the {{{./faq.html}FAQ}} and feel
- free to contact the {{{./mailing-lists.html}user mailing list}}. The posts to the mailing list are archived and could
- already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching
- the {{{./mailing-lists.html}mail archive}}.
+## Examples
- If you feel like the plugin is missing a feature or has a defect, you can submit a feature request or bug report in our
- {{{./issue-management.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of your
- concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason,
- entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated.
- Of course, patches are welcome, too. Contributors can check out the project from our
- {{{./scm.html}source repository}} and will find supplementary information in the
- {{{https://maven.apache.org/guides/development/guide-helping.html}guide to helping with Maven}}.
+To provide you with better understanding on some usages of the Clean Plugin, you can take a look into the following examples:
-* Examples
-
- To provide you with better understanding on some usages of the Clean Plugin,
- you can take a look into the following examples:
-
- * {{{./examples/delete_additional_files.html}How to delete additional files outside of
- the default directories?}}
-
- * {{{./examples/ignoring-errors.html}How to ignore clean errors?}}
-
- * {{{./examples/skipping-clean.html}How to skipping clean execution?}}
-
- []
+- [How to delete additional files outside of the default directories?](./examples/delete_additional_files.html)
+- [How to ignore clean errors?](./examples/ignoring-errors.html)
+- [How to skipping clean execution?](./examples/skipping-clean.html)
diff --git a/src/site/markdown/usage.md.vm b/src/site/markdown/usage.md.vm
index caf908f..2d02148 100644
--- a/src/site/markdown/usage.md.vm
+++ b/src/site/markdown/usage.md.vm
@@ -1,73 +1,55 @@
- ------
- Usage
- ------
- Edwin Punzalan
- ------
- 2006-06-29
- ------
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
+http://www.apache.org/licenses/LICENSE-2.0
-~~ NOTE: For help with the syntax of this file, see:
-~~ http://maven.apache.org/doxia/references/apt-format.html
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
-Usage
+# Usage
- The Maven Clean Plugin, as the name implies, attempts to clean the files and
- directories generated by Maven during its build. While there are plugins
- that generate additional files, the Clean Plugin assumes that these files are
- generated inside the <<<target>>> directory.
+The Maven Clean Plugin, as the name implies, attempts to clean the files and directories generated by Maven during its build. While there are plugins that generate additional files, the Clean Plugin assumes that these files are generated inside the `target` directory.
-* Cleaning a Maven project using the command-line
+Cleaning a Maven project using the command-line
+-----------------------------------------------
- The Clean Plugin can be called to execute in the command-line without any
- additional configurations. Like the other plugins, to run the Clean Plugin,
- you use:
+The Clean Plugin can be called to execute in the command-line without any additional configurations. Like the other plugins, to run the Clean Plugin, you use:
-+-----
+```shell
mvn clean:clean
-+-----
+```
- where the first <<<clean>>> refers to the plugin's alias, and the second
- <<<clean>>> refers to the plugin goal.
+where the first `clean` refers to the plugin's alias, and the second `clean` refers to the plugin goal.
- However, the Clean Plugin is a special plugin and is bound to its own special
- lifecycyle phase called <<<clean>>>. Thus, for simplicity, it can also be
- executed by using:
+However, the Clean Plugin is a special plugin and is bound to its own special lifecycyle phase called `clean`. Thus, for simplicity, it can also be executed by using:
-+-----
+```shell
mvn clean
-+-----
+```
- or with other phases/goals like:
+or with other phases/goals like:
-+-----
+```shell
mvn clean package site
-+-----
+```
-* Running the Clean Plugin automatically during a build
+Running the Clean Plugin automatically during a build
+-----------------------------------------------------
- If for some reason, adding <<<clean>>> to the command-line is not option,
- the Clean Plugin can be put into a project's <<<pom.xml>>> so that it gets executed
- everytime the project is built. Below is a sample <<<pom.xml>>> for running the
- Clean Plugin in the <<<initialize>>> phase everytime the project is built:
+If for some reason, adding `clean` to the command-line is not option, the Clean Plugin can be put into a project's `pom.xml` so that it gets executed everytime the project is built. Below is a sample `pom.xml` for running the Clean Plugin in the `initialize` phase everytime the project is built:
-+-----
+```xml
<project>
[...]
<build>
@@ -89,4 +71,4 @@ Usage
</build>
[...]
</project>
-+-----
+```
(maven-clean-plugin) 01/02: Rename the site documents ahead of converting them
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch maven-clean-plugin-3.x
in repository https://gitbox.apache.org/repos/asf/maven-clean-plugin.git
commit c3f2943cda193c6ff8b49b203f001da504ae0a64
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Thu Aug 6 13:52:57 2026 +0200
Rename the site documents ahead of converting them
A pure rename, so that git records it and `git log --follow` and `git blame` still
reach the history of each page after the conversion that follows. The content is
still APT at this point and the site does not build between the two commits.
---
.../examples/delete_additional_files.md.vm} | 0
.../ignoring-errors.apt.vm => markdown/examples/ignoring-errors.md.vm} | 0
.../skipping-clean.apt.vm => markdown/examples/skipping-clean.md.vm} | 0
src/site/{apt/index.apt.vm => markdown/index.md} | 0
src/site/{apt/usage.apt.vm => markdown/usage.md.vm} | 0
5 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/src/site/apt/examples/delete_additional_files.apt.vm b/src/site/markdown/examples/delete_additional_files.md.vm
similarity index 100%
rename from src/site/apt/examples/delete_additional_files.apt.vm
rename to src/site/markdown/examples/delete_additional_files.md.vm
diff --git a/src/site/apt/examples/ignoring-errors.apt.vm b/src/site/markdown/examples/ignoring-errors.md.vm
similarity index 100%
rename from src/site/apt/examples/ignoring-errors.apt.vm
rename to src/site/markdown/examples/ignoring-errors.md.vm
diff --git a/src/site/apt/examples/skipping-clean.apt.vm b/src/site/markdown/examples/skipping-clean.md.vm
similarity index 100%
rename from src/site/apt/examples/skipping-clean.apt.vm
rename to src/site/markdown/examples/skipping-clean.md.vm
diff --git a/src/site/apt/index.apt.vm b/src/site/markdown/index.md
similarity index 100%
rename from src/site/apt/index.apt.vm
rename to src/site/markdown/index.md
diff --git a/src/site/apt/usage.apt.vm b/src/site/markdown/usage.md.vm
similarity index 100%
rename from src/site/apt/usage.apt.vm
rename to src/site/markdown/usage.md.vm