-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
None
Currently CLI commands are run with a CommandContext loaded in a standard class loader. Launching a new process to execute commands in a modular class path allows commands defined in extensions to work. This will only work where WildFly can be found locally.
The options should probably be something like <executeLocal>true</executeLocal>. If no jboss-home is defined the server should be downloaded and in that environment. This does assume that's possible so testing needs to be done to confirm the behavior will work.
- is blocked by
-
WFMP-62 Execute CLI commands in a new process
- Resolved
- is incorporated by
-
WFMP-62 Execute CLI commands in a new process
- Resolved
- relates to
-
WFCORE-533 Handling of ModelControllerClient means there is no safe way to reload a process from the wildfly maven plugin
- Open