-
Notifications
You must be signed in to change notification settings - Fork 34
Closed
Description
It has been turned out that react and react-dom JAR has dependencies:
[INFO] +- org.webjars.npm:react:jar:16.8.6:runtime
[INFO] | +- org.webjars.npm:loose-envify:jar:1.4.0:runtime (version selected from constraint [1.1.0,2))
[INFO] | | \- org.webjars.npm:js-tokens:jar:4.0.0:runtime (version selected from constraint [3.0.0,4), [4.0.0,5))
[INFO] | +- org.webjars.npm:object-assign:jar:4.1.1:runtime (version selected from constraint [4.1.1,5))
[INFO] | +- org.webjars.npm:prop-types:jar:15.7.2:runtime (version selected from constraint [15.6.2,16))
[INFO] | | \- org.webjars.npm:react-is:jar:16.12.0:runtime (version selected from constraint [16.8.1,17))
[INFO] | \- org.webjars.npm:scheduler:jar:0.14.0-alpha.0:runtime (version selected from constraint [0.13.6,0.14))
These dependencies
- included into WAR
- seems not required/unused in our case
- are always tried to be resolved by Maven
The latter slows down build process as Maven always have to download them again and again.