From e0cdbdc475646b68d5e5ede485a385691bec1588 Mon Sep 17 00:00:00 2001 From: Jason van Zyl Date: Thu, 18 Dec 2008 04:29:15 +0000 Subject: [PATCH] o notes on how to improve the test so that it's easy to get others involved in adding/correcting the spec and accompanying tests. git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@727638 13f79535-47bb-0310-9956-ffa450edef68 --- .../apache/maven/project/builder/PomConstructionTest.java | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/maven-project/src/test/java/org/apache/maven/project/builder/PomConstructionTest.java b/maven-project/src/test/java/org/apache/maven/project/builder/PomConstructionTest.java index 1ec5723475..3e2d099539 100644 --- a/maven-project/src/test/java/org/apache/maven/project/builder/PomConstructionTest.java +++ b/maven-project/src/test/java/org/apache/maven/project/builder/PomConstructionTest.java @@ -36,6 +36,12 @@ public class PomConstructionTest mavenTools = lookup( MavenTools.class ); } + // Some better conventions for the test poms needs to be created and each of these tests + // that represent a verification of a specification item needs to be a couple lines at most. + // The expressions help a lot, but we need a clean to pick up a directory of POMs, automatically load + // them into a resolver, create the expression to extract the data to validate the Model, and the URI + // to validate the properties. We also need a way to navigate from the Tex specification documents to + // the test in question and vice versa. A little Eclipse plugin would do the trick. public void testThatAllPluginExecutionsWithIdsAreJoined() throws Exception {