maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From krosenv...@apache.org
Subject svn commit: r1422461 - /maven/shared/trunk/maven-shared-utils/src/site/apt/index.apt
Date Sun, 16 Dec 2012 03:30:38 GMT
Author: krosenvold
Date: Sun Dec 16 03:30:37 2012
New Revision: 1422461

URL: http://svn.apache.org/viewvc?rev=1422461&view=rev
Log:
o Addded 'why' to the site

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=1422461&r1=1422460&r2=1422461&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 Sun Dec 16 03:30:37 2012
@@ -35,6 +35,16 @@ Apache Maven Shared Utils
    It is not a 100% API compatible replacement though but a replacement <with improvements>:
    lots of methods got cleaned up, generics got added and we dropped a lot of unused code.
 
+Why ?
+
+   plexus-utils consisted mostly of code that was forked from various apache projects. From
a licensing
+   perspective this code became "unclean" when it was forked to codehaus. maven-shared-utils
is
+   based on the original from the apache sources.
+
+Why not commons ?
+    We would prefer code to use commons-* code where appropriate, but the plexus-utils became
+    slightly incompatible (different) from the commons over the years, so migrating is not
+    always a 1:1 operation. Migrating to maven-shared-utils is a 1:1 operation in most cases.
 
 Relation to Commons-*
 



Mime
View raw message