You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ol...@apache.org on 2018/08/29 04:18:06 UTC

[maven-site] branch master updated: Remove some Maven 1 history. (#33)

This is an automated email from the ASF dual-hosted git repository.

olamy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 76ca7d8  Remove some Maven 1 history. (#33)
76ca7d8 is described below

commit 76ca7d8bfb5469c6f522d99e0af8e6b287072a34
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Tue Aug 28 21:18:04 2018 -0700

    Remove some Maven 1 history. (#33)
    
    This was over a decade ago. Let's just specify what happens today.
---
 content/apt/guides/introduction/introduction-to-the-pom.apt | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/content/apt/guides/introduction/introduction-to-the-pom.apt b/content/apt/guides/introduction/introduction-to-the-pom.apt
index 6a11ede..144f010 100644
--- a/content/apt/guides/introduction/introduction-to-the-pom.apt
+++ b/content/apt/guides/introduction/introduction-to-the-pom.apt
@@ -71,10 +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/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
+ source directory, which is <<<src/test/java>>>; and so on. When executing a task or goal, Maven
  looks for the POM in the current directory. It reads the POM, gets the needed configuration information, then executes the
  goal.