-
Task
-
Resolution: Done
-
Minor
-
None
-
None
-
None
Currently the dependency of commons-io is defined in wildfly-core's root pom, and it is used as test dependency only in wildfly-core:
In WildFly Core's root pom
<version.commons-io>2.5</version.commons-io> ... <dependency> <groupId>commons-io</groupId> <artifactId>commons-io</artifactId> <version>${version.commons-io}</version> </dependency>
while it is used as a production dependency in WildFly:
In wildfly/ee-feature-pack/common/pom.xml
<dependency> <groupId>commons-io</groupId> <artifactId>commons-io</artifactId> </dependency>
The definition should be done in wildfly's root pom instead.
- split from
-
WFLY-14431 Do not use WildFly Core dependency management for dependencies that are test-only in core
- Closed