Hi Michael,
Are you aware that the preferred way to do this is by CMS[1][2]?
thanks,
Robert
[1] https://cms.apache.org/
[2] http://maven.apache.org/developers/website/index.html
Op Sat, 10 Jan 2015 20:17:32 +0100 schreef <[email protected]>:
Author: michaelo
Date: Sat Jan 10 19:17:32 2015
New Revision: 1650795
URL: http://svn.apache.org/r1650795
Log:
[MNGSITE-220] Wrong "test source directory" written in "Introduction to
the POM"
Modified:
maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt
Modified:
maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt?rev=1650795&r1=1650794&r2=1650795&view=diff
==============================================================================
---
maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt
(original)
+++
maven/site/trunk/content/apt/guides/introduction/introduction-to-the-pom.apt
Sat Jan 10 19:17:32 2015
@@ -71,7 +71,7 @@ Introduction to the POM
A Project Object Model or POM is the fundamental unit of work in
Maven. It is an XML file that contains information
about the project and configuration details used by Maven to build the
project. It contains default values for most projects.
Examples for this is the build directory, which is <<<target>>>; the
source directory, which is <<<src/main/java>>>; the test
- source directory, which is <<<src/main/test>>>; and so on.
+ source directory, which is <<<src/test/java>>>; and so on.
The POM was renamed from <<<project.xml>>> in Maven 1 to <<<pom.xml>>>
in Maven 2. Instead of having a <<<maven.xml>>> file that contains
the goals that can be executed, the goals or plugins are now
configured in the <<<pom.xml>>>. When executing a task or goal, Maven
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
