updated TODO
git-svn-id: https://svn.apache.org/repos/asf/maven/sandbox/trunk@1538440 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/dist-tools/dist-tool-plugin/src/main/resources/dist-tool.conf b/dist-tools/dist-tool-plugin/src/main/resources/dist-tool.conf
index f328dae..9e94a1f 100644
--- a/dist-tools/dist-tool-plugin/src/main/resources/dist-tool.conf
+++ b/dist-tools/dist-tool-plugin/src/main/resources/dist-tool.conf
@@ -2,8 +2,6 @@
## /directory: groupId[:parent-pom artifactId] [src+bin] [index page url]
## [*] artifactId [version restriction]
## * = only check info in index page, but not dist nor site (for plugins provided by components, like archetype, release, ...)
-#### site2X
-#### IP4 ASF (skin and parent find pattern hardcoded)
http://www.apache.org/dist/maven/
diff --git a/dist-tools/dist-tool-plugin/src/site/markdown/todo.md b/dist-tools/dist-tool-plugin/src/site/markdown/todo.md
index 39b42d4..6f83d2a 100644
--- a/dist-tools/dist-tool-plugin/src/site/markdown/todo.md
+++ b/dist-tools/dist-tool-plugin/src/site/markdown/todo.md
@@ -1,35 +1,25 @@
Todo
====
-### Source Release
+### Index Pages
-* Option to fail the build (or separate goal), so we don't have to check the report daily, but let the CI server mail when failing.
- * notice that failing the build will make the report unusable: so we must have either a separate goal or a mail sent explicitely from plugin
- * there are some known issues with old artifacts, which don't have newer version expected: need to configure these as "accepted exceptions"
-
-
-### Sites
-
-* Check if artifact versions are up to date in listing pages:
- * http://maven.apache.org/plugins/
- * http://maven.apache.org/shared/
- * http://maven.apache.org/pom/
- * http://maven.apache.org/skins/
-pom listing handled ugly hardcoded way :(
-
-Start think on a more database way of storing infos.
- * sources may contains artifacts,artifact may be on listings listing may have categories ...
-
-* Option to fail the build (or separate goal), so we don't have to check the report daily, but let the CI server mail when failing
+* path detection for some parent POMs (ASF, Maven) handled ugly hardcoded way :(
# Done
-* take screenshot of site. ( os specific )
-
* See where to publish the result on Maven site
* jenkins site URL https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site
+* take screenshot of site. ( os specific )
+
+* Separate goal to fail the build, so we don't have to check the report daily, but let the CI server mail when failing.
+ * notice that failing the build will make the report unusable: so we must have either a separate goal or a mail sent explicitely from plugin
+ * there are some known issues with old artifacts, which don't have newer version expected: need to configure these as "accepted exceptions"
+
+* dist-tool.conf format as a DSL to organize distribution area check rules
+
### Source Release
+
* add date of release (from artifact)
* date from metadata is ok ?
@@ -40,10 +30,19 @@
### Sites
* add date of site
- * [sky] date from comment part in skin (no always ok :( )
+ * [sky] date from comment part in skin (not always ok :( )
* remove "check if version present", since our inheritance ensures we don't have problems
* [sky] kept only for precise layout check
* replace Skins columns with one unique column "Skin used", showing which skin is used (with version)
* [sky] no garantee some site like http://maven.apache.org/plugins/maven-one-plugin/ have no style header
* add date of release (from artifact)
* [sky] date from metadata is ok ?
+
+### Index Pages
+
+* Check if artifact versions are up to date in listing pages:
+ * http://maven.apache.org/plugins/
+ * http://maven.apache.org/shared/
+ * http://maven.apache.org/pom/
+ * http://maven.apache.org/skins/
+
\ No newline at end of file
