>> It is also picked up automatically with scope=provided.
>Useful to know; the Maven documentation is not explicit on that.
>The name makes it sound as though the user has to provide the jar themselves.
You're right, the user has to provide the jar themselves. But only if it's
_needed_ at runtim
+1 Downstream projects take transitive dependencies without looking why they
are needed and if they are needed. One of the root causes for the dependency
(version) hell.
-Ursprüngliche Nachricht-
Von: Matt Sicker
Gesendet: Dienstag, 2. Februar 2021 17:35
An: Commons Developers List
Be
Hello Gary,
finally, I found it. It seems to be related to the underlying OS or filesystem.
I filed a bug and created a patch:
https://issues.apache.org/jira/browse/IO-701
https://github.com/apache/commons-io/pull/186
Could you please review it and consider the plan for a 2.9.0 version?
Kind r
Hello Gary,
some more detailed testing. In general:
mvn clean install -Drelease -DallTests -Dmaven.test.failure.ignore=true
Run from main directory. Don't miss -Drelease -DallTests here. You can use Java
8 or 11, both is used in RedHats CI environment.
===
Windows Setup
=
Hello Gary,
thanks for your advice. All test mentioned run fine with commons-io 2.5,
addressing it here seems right.
There are new issues with the current 2.9.0-snapshot. Previously with 2.8.0 it
was
https://github.com/wildfly/wildfly-core/blob/ce3b0e1b66ac39c1832dfea1735069e17bbc4fe1/testsuit
Dear IO developers,
you already fixed https://issues.apache.org/jira/browse/IO-692 The underlying
issue blocks the component upgrade in WildFly Core, due to a breaking
integration unit test. (Pull is here:
https://github.com/wildfly/wildfly-core/pull/4400 ) It would be great to have
the new en
