Github user asfgit closed the pull request at:
https://github.com/apache/maven-shared/pull/13
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Am 07/02/16 um 16:59 schrieb Robert Scholte:
>
> I agree that this should have been commons-io:2.4, but it matches the
> documentation (g:a is unique and nearest wins). I expect that the problem
> lies in the way Aether is used.
> I assume that first the complete dependency graph is collected
On Sat, 02 Jul 2016 16:31:41 +0200, Christian Schulte
wrote:
Am 07/02/16 um 15:25 schrieb Robert Scholte:
Hi,
It is very likely that a previous version of maven-shared-utils did not
depend on commons-io, which made it required to specify commons-io with
the test-scope for this project.
Th
Am 07/02/16 um 15:25 schrieb Robert Scholte:
> Hi,
>
> It is very likely that a previous version of maven-shared-utils did not
> depend on commons-io, which made it required to specify commons-io with
> the test-scope for this project.
That's what I assume as well.
> With this in mind it see
Hi,
there's this basic rule: always specify your direct dependencies if you
use them in your code, never rely on transitive dependencies.
So in this case commons-io is not directly used by the main classes, but
it is by the test-classes.
It is very likely that a previous version of maven-shar
