-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
1.0.2.Final
-
None
-
-
Windows Container Support for Red Hat OpenShift
WildFly Flow CLI ignores Maven specific settings that are required to employ local mirrors, and other common setups behind corporate networks.
https://maven.apache.org/configure.html
Both WildFly Maven Plugin & Galleon Maven Plugin allow configurations via:
- USER_HOME/.m2/settings.xml
- .mvn/maven_config
- MAVEN_OPTS
- MAVEN_ARGS
Galleon CLI allow configurations via:
- galleon.sh maven set-settings-file ${USER_HOME}/.m2/settings.xml
But WildFly Glow currently doesn't allow for specific Maven Settings except only for 'maven.local.repo' via JAVA_OPTS
This results in WildFly Glow unusable behind a corporate firewall.
Thus then please consider (instead of extending) to unify in a single shared maven library in for all WildFly Maven tools to rely from a single Maven Global Settings, while in case of specific tools changes also allow for specific Maven Local Settings.
ps: Meanwhile is there a workaround to download all artifacts required by WildFly Glow via WildFly Maven Plugin or WildFly Galleon, so that then can find all in place in 'maven.local.repo' or else ?