Skip to content

docs: grammar #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
elharo merged 1 commit into from
Feb 23, 2020
Merged

docs: grammar #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/site/apt/index.apt.vm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,12 +40,12 @@ ${project.name}

Why?

plexus-utils consisted mostly of code that was forked from various apache projects.
plexus-utils consisted mostly of code that was forked from various Apache projects.
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
We would prefer code to use commons-* 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.

Expand All @@ -55,7 +55,7 @@ Relation to 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-io classes directly. Most times it's sufficient
to just create an empty subclass and expose that instead.
avoid exposing commons-io classes directly. Most times it's sufficient
to create an empty subclass and expose that instead.

[]