You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by el...@apache.org on 2020/03/21 14:37:04 UTC
[maven-shared-utils] branch elharo-patch-1 created (now 7e970e1)
This is an automated email from the ASF dual-hosted git repository.
elharo pushed a change to branch elharo-patch-1
in repository https://gitbox.apache.org/repos/asf/maven-shared-utils.git.
at 7e970e1 docs: we don't shade commons-io
This branch includes the following new commits:
new 7e970e1 docs: we don't shade commons-io
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
[maven-shared-utils] 01/01: docs: we don't shade commons-io
Posted by el...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch elharo-patch-1
in repository https://gitbox.apache.org/repos/asf/maven-shared-utils.git
commit 7e970e162cd11b4f6d605708b7f434672524b028
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Sat Mar 21 10:36:57 2020 -0400
docs: we don't shade commons-io
@hboutemy
Maybe we used to, but not anymore.
---
src/site/apt/index.apt.vm | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/src/site/apt/index.apt.vm b/src/site/apt/index.apt.vm
index 0ee0872..419146d 100644
--- a/src/site/apt/index.apt.vm
+++ b/src/site/apt/index.apt.vm
@@ -49,13 +49,4 @@ Why not commons?
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-*
-
- 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 exposing commons-io classes directly. Most times it's sufficient
- to create an empty subclass and expose that instead.
-
[]