[maven-site] branch master updated: assume no one is still using 2.0.9 or earlier (#38)

[ol...@apache.org]

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 e56dfea  assume no one is still using 2.0.9 or earlier (#38)
e56dfea is described below

commit e56dfea7b2e24fecea61cfed6aad7859296a7681
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Thu Sep 20 22:23:34 2018 -0400

    assume no one is still using 2.0.9 or earlier (#38)
---
 .../apt/guides/introduction/introduction-to-dependency-mechanism.apt  | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
index dc03779..7a2d313 100644
--- a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
+++ b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
@@ -134,7 +134,7 @@ Introduction to the Dependency Mechanism
    which contains it explicitly. The artifact is always available and is not
    looked up in a repository.
 
- * <<import>> <(only available in Maven 2.0.9 or later)>\
+ * <<import>>\
    This scope is only supported on a dependency of type <<<pom>>> in the <<<\<dependencyManagement\>>>> section. It
    indicates the dependency to be replaced with the effective list of dependencies in the specified POM's
    <<<\<dependencyManagement\>>>> section. Since they are replaced, dependencies with a scope of <<<import>>> do not
@@ -434,8 +434,6 @@ Introduction to the Dependency Mechanism
 
 ** {Importing Dependencies}
 
- <The features defined in this section are only available in Maven 2.0.9 or later. This means that poms declaring the import scope will not be parseable by earlier versions of Maven. Weigh this information carefully before deciding to use it. If you do use it, we suggest you use the enforcer plugin to require a minimum Maven version of 2.0.9.>
-
  The examples in the previous section describe how to specify managed dependencies through inheritence. However,
  in larger projects it may be impossible to accomplish this since a project can only inherit from a single parent.
  To accommodate this, projects can import managed dependencies from other projects. This is accomplished by declaring a