Description of problem: A regression has been introduced by the bz991469 fix. It breaks module add command included in a CLI module archive. For details see https://issues.jboss.org/browse/WFLY-1913?focusedCommentId=12808246&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12808246 Version-Release number of selected component (if applicable): EAP 6.2.0.ER1 How reproducible: Create a CLI module archive which includes 'module add' command involving a resource taken from the module archive. An example of such an archive can be found at WFLY-1913.
Relevant PR: https://github.com/jbossas/jboss-eap/pull/509
Ivo Studensky <istudens> made a comment on jira WFLY-1913 Merged.
Created attachment 813260 [details] Test CLI deployment archive
Hi Ivo, How about the error message after undeploy operation? ERROR [org.jboss.as.cli.CommandContext] Failed to execute archive script: JBAS014746: steps may not be null Failed to execute archive script: JBAS014746: steps may not be null All commands inside undeploy.scr are successfully executed, but after that this message will appear (same on win and linux, same message with 6.1.1). Is this a known issue or something wrong with CLI archive? Just use attachment 813260 [details] [standalone@localhost:9999 /] deploy --path=~/Downloads/install-mojarra-2.0.0.cli [standalone@localhost:9999 /] undeploy --path=~/Downloads/install-mojarra-2.0.0.cli Failed to execute archive script: JBAS014746: steps may not be null Thanks. Verified on EAP 6.2.0.ER6. 'module add' command inside CLI deployment archive now works on Windows as expected.
Petr, your deploy.scr/undeploy.src files are missing any 'deploy' step which is the cause of the warning you see.