[jboss-svn-commits] JBL Code SVN: r12933 - in labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src: main/site and 6 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Thu Jun 28 15:48:04 EDT 2007
Author: steve.ebersole at jboss.com
Date: 2007-06-28 15:48:04 -0400 (Thu, 28 Jun 2007)
New Revision: 12933
Added:
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/examples/
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/examples/basic.apt
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/index.apt
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/usage.apt
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/fml/
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/fml/faq.fml
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/site.xml
Removed:
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/examples/basic.apt
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/index.apt
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/usage.apt
labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/site.xml
Log:
corrected site documentation location
Deleted: labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/examples/basic.apt
===================================================================
--- labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/examples/basic.apt 2007-06-28 18:15:40 UTC (rev 12932)
+++ labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/examples/basic.apt 2007-06-28 19:48:04 UTC (rev 12933)
@@ -1,69 +0,0 @@
- ------
- Basic Setup
- ------
- Steve Ebersole
- ------
- 28 June 2007
- ------
-
-~~ Copyright (c) 2007 Red Hat Middleware, LLC. All rights reserved.
-~~
-~~ This copyrighted material is made available to anyone wishing to use, modify,
-~~ copy, or redistribute it subject to the terms and conditions of the GNU
-~~ Lesser General Public License, v. 2.1. This program is distributed in the
-~~ hope that it will be useful, but WITHOUT A WARRANTY; without even the implied
-~~ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-~~ Lesser General Public License for more details. You should have received a
-~~ copy of the GNU Lesser General Public License, v.2.1 along with this
-~~ distribution; if not, write to the Free Software Foundation, Inc.,
-~~ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-~~
-~~ Red Hat Author(s): Steve Ebersole
-
-Basic Setup
-
- In order to have the <Test Environment Extension Plugin> extend the test
- environment, users must define one or more environments and then tell the
- <Test Environment Extension Plugin> where to find those environments as
- well as which environment to use for a particular test suite run.
-
-* Define environment(s)
-
- Environments are defined in XML format. Here is an example to define
- some dependencies and resources specific to a database from venerable
- acme.com:
-+-----+
-<environments>
- <environment name="hsqldb">
- <testResources>
- <testResource>
- <directory>environment/acme</directory>
- <filtering>false</filtering>
- <includes>
- <include>*.xml</include>
- <include>*.properties</include>
- </includes>
- </testResource>
- </testResources>
- <dependencies>
- <dependency>
- <groupId>com.acme</groupId>
- <artifactId>acme-db</artifactId>
- <version>1.0</version>
- </dependency>
- </dependencies>
- </environment>
-</environments>
-+-----+
-
- Within the \<environment/\> tag, we see \<testResources/\> and \<depedencies/\>
- both of which follow the allowable syntax of their general Maven counterparts.
- It is important to note, however, that any resources and dependencies defined
- via this mechanism are implicitly added to the <<test>> classpath.
-
-* Use specific environment during test
-
- The anticipated usage of this plugin would specify using properties to
- control the declaration of the environment to use. For example, to use
- the environment we defined above, we would do
- <<<mvn test -Dtest.extender.cfg=path-to-env-file.xml -Dtest.extender.env=acme>>>
\ No newline at end of file
Deleted: labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/index.apt
===================================================================
--- labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/index.apt 2007-06-28 18:15:40 UTC (rev 12932)
+++ labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/index.apt 2007-06-28 19:48:04 UTC (rev 12933)
@@ -1,61 +0,0 @@
- ------
- Introduction
- ------
- Steve Ebersole
- ------
- 28 June 2007
- ------
-
-~~ Copyright © 2007 Red Hat Middleware, LLC. All rights reserved.
-~~
-~~ This copyrighted material is made available to anyone wishing to use, modify,
-~~ copy, or redistribute it subject to the terms and conditions of the GNU
-~~ Lesser General Public License, v. 2.1. This program is distributed in the
-~~ hope that it will be useful, but WITHOUT A WARRANTY; without even the implied
-~~ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-~~ Lesser General Public License for more details. You should have received a
-~~ copy of the GNU Lesser General Public License, v.2.1 along with this
-~~ distribution; if not, write to the Free Software Foundation, Inc.,
-~~ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-~~
-~~ Red Hat Author(s): Steve Ebersole
-
-Test Environment Extension Plugin
-
- Maven has great support for running tests through Surefire. However, one
- feature it does lack is the ability for users to extend the test classpath
- beyond what the project POM defines.
-
- Consider a test suite which must be run against a number of databases.
- Database-related tests typically require access to driver jars and various
- resource files on the classpath to function properly. Maven handles this
- fine when all the ingredients are known ahead of time. But say someone
- other than the project team wants to run that test suite against a database
- other than the ones defined by dependencies/resources in the POM... How
- can they do it? The answer is that they currently (pre Maven 2.1) cannot
- without modifying the project POM.
-
- A logical answer would seem to be using profiles.xml to add these extra
- classpath elements. But the problem is that profiles.xml does not allow
- definition of dependencies (actually, 2.1 will allow users to define
- <<test>> dependencies in profiles.xml. With the release of 2.1, this plugin
- becomes obsolete.
-
- Until that time, we define a parallel extension approach, via some "extra"
- XML allowing project teams to allow their test environments to be
- extended/expanded.
-
-* Goals Overview
- This plugin defines only a single goal:
- {{{extend.html}maven-test-ext-plugin:extend}} reads the extra XML and
- extends the projects test classpath accordingly.
-
-* Usage
-
- Instructions on how to use the <Test Environment Extension Plugin> can be found {{{usage.html}here}}.
-
-* Examples
-
- The main thing with the <Test Environment Extension Plugin> is setting up
- and then using the environments. Here is an {{{examples/basic.html}example}}
- of doing that.
Deleted: labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/usage.apt
===================================================================
--- labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/usage.apt 2007-06-28 18:15:40 UTC (rev 12932)
+++ labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/usage.apt 2007-06-28 19:48:04 UTC (rev 12933)
@@ -1,57 +0,0 @@
- ------
- Usage
- ------
- Steve Ebersole
- ------
- 28 June 2007
- ------
-
-~~ Copyright (c) 2007 Red Hat Middleware, LLC. All rights reserved.
-~~
-~~ This copyrighted material is made available to anyone wishing to use, modify,
-~~ copy, or redistribute it subject to the terms and conditions of the GNU
-~~ Lesser General Public License, v. 2.1. This program is distributed in the
-~~ hope that it will be useful, but WITHOUT A WARRANTY; without even the implied
-~~ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-~~ Lesser General Public License for more details. You should have received a
-~~ copy of the GNU Lesser General Public License, v.2.1 along with this
-~~ distribution; if not, write to the Free Software Foundation, Inc.,
-~~ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-~~
-~~ Red Hat Author(s): Steve Ebersole
-
-Usage
-
- The <Test Environment Extension Plugin> aims to allow project teams the
- ability to let their project's users extend the project's test environment
- in an extensible manner. For a full discussion of this intention, see
- the {{{index.html}Introduction}}.
-
-* Minimal configuration
-
- The plugin defines only a single goal (extend) which has pretty minimal
- configuration options. The basic configuration from a project team's
- perspective is to simply name the plugin in the project's build plugins:
-+-----+
-<project>
- ...
- <build>
- <plugins>
- <plugin>
- <groupId>org.jboss.maven.plugins</groupId>
- <artifactId>maven-test-ext-plugin</artifactId>
- </plugin>
- </plugins>
- ...
- </build>
- ...
-</project>
-+-----+
-
-* Environment Configuration
-
- The <Test Environment Extension Plugin> does define two configuration
- options, which are anticipated to be set through properties rather than
- directly in the plugin configuration. See the {{{extend.html}goal}}
- documentation for discussion of the <extenderConfig> and <extenderEnv>
- parameters.
\ No newline at end of file
Deleted: labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/site.xml
===================================================================
--- labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/site.xml 2007-06-28 18:15:40 UTC (rev 12932)
+++ labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/site.xml 2007-06-28 19:48:04 UTC (rev 12933)
@@ -1,34 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- ~ Copyright (c) 2007, Red Hat Middleware, LLC. All rights reserved.
- ~
- ~ This copyrighted material is made available to anyone wishing to use, modify,
- ~ copy, or redistribute it subject to the terms and conditions of the GNU
- ~ Lesser General Public License, v. 2.1. This program is distributed in the
- ~ hope that it will be useful, but WITHOUT A WARRANTY; without even the implied
- ~ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- ~ Lesser General Public License for more details. You should have received a
- ~ copy of the GNU Lesser General Public License, v.2.1 along with this
- ~ distribution; if not, write to the Free Software Foundation, Inc.,
- ~ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
- ~
- ~ Red Hat Author(s): Steve Ebersole
- -->
-<project name="Maven">
-
- <body>
- <menu name="Overview">
- <item name="Introduction" href="index.html"/>
- <item name="Goals" href="plugin-info.html"/>
- <item name="Usage" href="usage.html"/>
- <item name="FAQ" href="faq.html"/>
- </menu>
-
- <menu name="Examples">
- <item name="Basic Setup" href="examples/basic.html"/>
- </menu>
-
- ${reports}
- </body>
-
-</project>
Copied: labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/examples/basic.apt (from rev 12929, labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/examples/basic.apt)
===================================================================
--- labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/examples/basic.apt (rev 0)
+++ labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/examples/basic.apt 2007-06-28 19:48:04 UTC (rev 12933)
@@ -0,0 +1,73 @@
+ ------
+ Basic Setup
+ ------
+ Steve Ebersole
+ ------
+ 28 June 2007
+ ------
+
+~~ Copyright (c) 2007 Red Hat Middleware, LLC. All rights reserved.
+~~
+~~ This copyrighted material is made available to anyone wishing to use, modify,
+~~ copy, or redistribute it subject to the terms and conditions of the GNU
+~~ Lesser General Public License, v. 2.1. This program is distributed in the
+~~ hope that it will be useful, but WITHOUT A WARRANTY; without even the implied
+~~ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+~~ Lesser General Public License for more details. You should have received a
+~~ copy of the GNU Lesser General Public License, v.2.1 along with this
+~~ distribution; if not, write to the Free Software Foundation, Inc.,
+~~ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+~~
+~~ Red Hat Author(s): Steve Ebersole
+
+Basic Setup
+
+ In order to have the <Test Environment Extension Plugin> extend the test
+ environment, users must define one or more environments and then tell the
+ <Test Environment Extension Plugin> where to find those environments as
+ well as which environment to use for a particular test suite run.
+
+* Define environment(s)
+
+ Environments are defined in XML format. Here is an example to define
+ some dependencies and resources specific to a database from venerable
+ acme.com:
+
++-----+
+<environments>
+ <environment name="hsqldb">
+ <testResources>
+ <testResource>
+ <directory>environment/acme</directory>
+ <filtering>false</filtering>
+ <includes>
+ <include>*.xml</include>
+ <include>*.properties</include>
+ </includes>
+ </testResource>
+ </testResources>
+ <dependencies>
+ <dependency>
+ <groupId>com.acme</groupId>
+ <artifactId>acme-db</artifactId>
+ <version>1.0</version>
+ </dependency>
+ </dependencies>
+ </environment>
+</environments>
++-----+
+
+ Within the \<environment/\> tag, we see \<testResources/\> and \<depedencies/\>
+ both of which follow the allowable syntax of their general Maven counterparts.
+ It is important to note, however, that any resources and dependencies defined
+ via this mechanism are implicitly added to the <<test>> classpath.
+
+* Use specific environment during test
+
+ The anticipated usage of this plugin would specify using properties to
+ control the declaration of the environment to use. For example, to use
+ the environment we defined above, we would issue the following:
+
++-----+
+mvn test -Dtest.extender.cfg=path-to-env-file.xml -Dtest.extender.env=acme
++-----+
\ No newline at end of file
Copied: labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/index.apt (from rev 12929, labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/index.apt)
===================================================================
--- labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/index.apt (rev 0)
+++ labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/index.apt 2007-06-28 19:48:04 UTC (rev 12933)
@@ -0,0 +1,61 @@
+ ------
+ Introduction
+ ------
+ Steve Ebersole
+ ------
+ 28 June 2007
+ ------
+
+~~ Copyright © 2007 Red Hat Middleware, LLC. All rights reserved.
+~~
+~~ This copyrighted material is made available to anyone wishing to use, modify,
+~~ copy, or redistribute it subject to the terms and conditions of the GNU
+~~ Lesser General Public License, v. 2.1. This program is distributed in the
+~~ hope that it will be useful, but WITHOUT A WARRANTY; without even the implied
+~~ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+~~ Lesser General Public License for more details. You should have received a
+~~ copy of the GNU Lesser General Public License, v.2.1 along with this
+~~ distribution; if not, write to the Free Software Foundation, Inc.,
+~~ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+~~
+~~ Red Hat Author(s): Steve Ebersole
+
+Test Environment Extension Plugin
+
+ Maven has great support for running tests through Surefire. However, one
+ feature it does lack is the ability for users to extend the test classpath
+ beyond what the project POM defines.
+
+ Consider a test suite which must be run against a number of databases.
+ Database-related tests typically require access to driver jars and various
+ resource files on the classpath to function properly. Maven handles this
+ fine when all the ingredients are known ahead of time. But say someone
+ other than the project team wants to run that test suite against a database
+ other than the ones defined by dependencies/resources in the POM... How
+ can they do it? The answer is that they currently (pre Maven 2.1) cannot
+ without modifying the project POM.
+
+ A logical answer would seem to be using profiles.xml to add these extra
+ classpath elements. But the problem is that profiles.xml does not allow
+ definition of dependencies (actually, 2.1 will allow users to define
+ <<test>> dependencies in profiles.xml. With the release of 2.1, this plugin
+ becomes obsolete.
+
+ Until that time, we define a parallel extension approach, via some "extra"
+ XML allowing project teams to allow their test environments to be
+ extended/expanded.
+
+* Goals Overview
+
+ This plugin defines only a single goal, {{{extend-mojo.html}test-ext:extend}},
+ which reads the extra XML and extends the projects test classpath accordingly.
+
+* Usage
+
+ Instructions on how to use the <Test Environment Extension Plugin> can be found {{{usage.html}here}}.
+
+* Examples
+
+ The main thing with the <Test Environment Extension Plugin> is setting up
+ and then using the environments. Here is an {{{examples/basic.html}example}}
+ of doing that.
Copied: labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/usage.apt (from rev 12929, labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/apt/usage.apt)
===================================================================
--- labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/usage.apt (rev 0)
+++ labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/apt/usage.apt 2007-06-28 19:48:04 UTC (rev 12933)
@@ -0,0 +1,58 @@
+ ------
+ Usage
+ ------
+ Steve Ebersole
+ ------
+ 28 June 2007
+ ------
+
+~~ Copyright (c) 2007 Red Hat Middleware, LLC. All rights reserved.
+~~
+~~ This copyrighted material is made available to anyone wishing to use, modify,
+~~ copy, or redistribute it subject to the terms and conditions of the GNU
+~~ Lesser General Public License, v. 2.1. This program is distributed in the
+~~ hope that it will be useful, but WITHOUT A WARRANTY; without even the implied
+~~ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+~~ Lesser General Public License for more details. You should have received a
+~~ copy of the GNU Lesser General Public License, v.2.1 along with this
+~~ distribution; if not, write to the Free Software Foundation, Inc.,
+~~ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+~~
+~~ Red Hat Author(s): Steve Ebersole
+
+Usage
+
+ The <Test Environment Extension Plugin> aims to allow project teams the
+ ability to let their project's users extend the project's test environment
+ in an extensible manner. For a full discussion of this intention, see
+ the {{{index.html}Introduction}}.
+
+* Minimal configuration
+
+ The plugin defines only a single goal (extend) which has pretty minimal
+ configuration options. The basic configuration from a project team's
+ perspective is to simply name the plugin in the project's build plugins:
+
++-----+
+<project>
+ ...
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.jboss.maven.plugins</groupId>
+ <artifactId>maven-test-ext-plugin</artifactId>
+ </plugin>
+ </plugins>
+ ...
+ </build>
+ ...
+</project>
++-----+
+
+* Environment Configuration
+
+ The <Test Environment Extension Plugin> does define two configuration
+ options, which are anticipated to be set through properties rather than
+ directly in the plugin configuration. See the {{{extend.html}goal}}
+ documentation for discussion of the <extenderConfig> and <extenderEnv>
+ parameters.
\ No newline at end of file
Added: labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/fml/faq.fml
===================================================================
--- labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/fml/faq.fml (rev 0)
+++ labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/fml/faq.fml 2007-06-28 19:48:04 UTC (rev 12933)
@@ -0,0 +1,35 @@
+<?xml version="1.0"?>
+<!--
+ ~ Copyright (c) 2007, Red Hat Middleware, LLC. All rights reserved.
+ ~
+ ~ This copyrighted material is made available to anyone wishing to use, modify,
+ ~ copy, or redistribute it subject to the terms and conditions of the GNU
+ ~ Lesser General Public License, v. 2.1. This program is distributed in the
+ ~ hope that it will be useful, but WITHOUT A WARRANTY; without even the implied
+ ~ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ ~ Lesser General Public License for more details. You should have received a
+ ~ copy of the GNU Lesser General Public License, v.2.1 along with this
+ ~ distribution; if not, write to the Free Software Foundation, Inc.,
+ ~ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+ ~
+ ~ Red Hat Author(s): Steve Ebersole
+ -->
+<faqs id="FAQ" title="Frequently Asked Questions">
+ <part id="General">
+ <faq id="profiles">
+ <question>Why not just use profiles?</question>
+ <answer>
+ <p>
+ Using profiles would indeed be the preferred way to achieve this
+ functionality. Unfortunately, at the time of writing this
+ plugin, profiles did not support defining dependencies. Or
+ more correctly, profiles.xml does not; the profiles in pom.xml
+ do in fact allow that, but then we would lose the extensibility
+ aspect of this plugins goals. It is my understanding that
+ this will be a feature of profiles.xml starting in
+ Maven 2.1.
+ </p>
+ </answer>
+ </faq>
+ </part>
+</faqs>
\ No newline at end of file
Copied: labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/site.xml (from rev 12929, labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/main/site/site.xml)
===================================================================
--- labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/site.xml (rev 0)
+++ labs/jbossbuild/maven-plugins/trunk/maven-test-ext-plugin/src/site/site.xml 2007-06-28 19:48:04 UTC (rev 12933)
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ~ Copyright (c) 2007, Red Hat Middleware, LLC. All rights reserved.
+ ~
+ ~ This copyrighted material is made available to anyone wishing to use, modify,
+ ~ copy, or redistribute it subject to the terms and conditions of the GNU
+ ~ Lesser General Public License, v. 2.1. This program is distributed in the
+ ~ hope that it will be useful, but WITHOUT A WARRANTY; without even the implied
+ ~ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ ~ Lesser General Public License for more details. You should have received a
+ ~ copy of the GNU Lesser General Public License, v.2.1 along with this
+ ~ distribution; if not, write to the Free Software Foundation, Inc.,
+ ~ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+ ~
+ ~ Red Hat Author(s): Steve Ebersole
+ -->
+<project name="Maven">
+
+ <body>
+ <menu name="Overview">
+ <item name="Introduction" href="index.html"/>
+ <item name="Goals" href="plugin-info.html"/>
+ <item name="Usage" href="usage.html"/>
+ <item name="FAQ" href="faq.html"/>
+ </menu>
+
+ <menu name="Examples">
+ <item name="Basic Setup" href="examples/basic.html"/>
+ </menu>
+
+ ${reports}
+ </body>
+
+</project>
More information about the jboss-svn-commits
mailing list