maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hbout...@apache.org
Subject svn commit: r1404026 - /maven/shared/trunk/maven-shared-utils/src/site/apt/index.apt
Date Wed, 31 Oct 2012 08:30:38 GMT
Author: hboutemy
Date: Wed Oct 31 08:30:38 2012
New Revision: 1404026

URL: http://svn.apache.org/viewvc?rev=1404026&view=rev
Log:
o added link to commons-io
o fixed typos

Modified:
    maven/shared/trunk/maven-shared-utils/src/site/apt/index.apt

Modified: maven/shared/trunk/maven-shared-utils/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/maven/shared/trunk/maven-shared-utils/src/site/apt/index.apt?rev=1404026&r1=1404025&r2=1404026&view=diff
==============================================================================
--- maven/shared/trunk/maven-shared-utils/src/site/apt/index.apt (original)
+++ maven/shared/trunk/maven-shared-utils/src/site/apt/index.apt Wed Oct 31 08:30:38 2012
@@ -38,9 +38,9 @@ Apache Maven Shared Utils
 
 Relation to Commons-*
 
-  maven-shared-utils internally use commons-io. We shade all commons
-  classes into our own private package to prevent classpatch clashes.
+  maven-shared-utils internally use {{{http://commons.apache.org/io/}commons-io}}. We shade
all commons
+  classes into our own private package to prevent classpath clashes.
 
   This is the reason why any public API in maven-shared-utils must
-  avoid to expose commons classe directly. Most times it's sufficient
+  avoid to expose commons-io classes directly. Most times it's sufficient
   to just create an empty subclass and expose that instead.



Mime
View raw message