[
https://issues.jboss.org/browse/JBASMP-68?page=com.atlassian.jira.plugin....
]
Václav Chalupa commented on JBASMP-68:
--------------------------------------
Is planned any progress with this issue for WildFly maven plugin?
execute-commands does not work for module command
-------------------------------------------------
Key: JBASMP-68
URL:
https://issues.jboss.org/browse/JBASMP-68
Project: JBoss AS Maven Plugins
Issue Type: Bug
Affects Versions: 7.6.Final
Reporter: Alfio Gloria
Assignee: James Perkins
I'm trying to remove a jboss module by means of maven.
{code:xml}
<configuration>
<jbossHome>${project.build.directory}/server/jboss72</jbossHome>
<execute-commands>
<commands>
<command>module remove --slot=main
--name=system.layers.base.org.jboss.weld.core</command>
</commands>
</execute-commands>
</configuration>
{code}
execute-commands fails with the following stack trace:
{code}
Failed to execute goal
org.jboss.as.plugins:jboss-as-maven-plugin:7.5.Final:execute-commands
(install-patched-weld) on project tools: Execution install-patched-weld of goal
org.jboss.as.plugins:jboss-as-maven-plugin:7.5.Final:execute-commands failed: Command
execution failed for command 'module remove --slot=main
--name=system.layers.base.org.jboss.weld.core'. JBOSS_HOME environment variable is not
set. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.jboss.as.plugins:jboss-as-maven-plugin:7.5.Final:execute-commands
(install-patched-weld) on project tools: Execution install-patched-weld of goal
org.jboss.as.plugins:jboss-as-maven-plugin:7.5.Final:execute-commands failed: Command
execution failed for command 'module remove --slot=main
--name=system.layers.base.org.jboss.weld.core'. JBOSS_HOME environment variable is not
set.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
install-patched-weld of goal
org.jboss.as.plugins:jboss-as-maven-plugin:7.5.Final:execute-commands failed: Command
execution failed for command 'module remove --slot=main
--name=system.layers.base.org.jboss.weld.core'. JBOSS_HOME environment variable is not
set.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.IllegalArgumentException: Command execution failed for command
'module remove --slot=main --name=system.layers.base.org.jboss.weld.core'.
JBOSS_HOME environment variable is not set.
at org.jboss.as.plugin.cli.Commands.executeCommands(Commands.java:180)
at org.jboss.as.plugin.cli.Commands.execute(Commands.java:134)
at org.jboss.as.plugin.cli.ExecuteCommands.execute(ExecuteCommands.java:71)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
... 20 more
Caused by: org.jboss.as.cli.CommandLineException: JBOSS_HOME environment variable is not
set.
at
org.jboss.as.cli.handlers.module.ASModuleHandler.getModulesDir(ASModuleHandler.java:362)
at
org.jboss.as.cli.handlers.module.ASModuleHandler.removeModule(ASModuleHandler.java:326)
at org.jboss.as.cli.handlers.module.ASModuleHandler.doHandle(ASModuleHandler.java:214)
at
org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:86)
at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:581)
at org.jboss.as.plugin.cli.Commands.executeCommands(Commands.java:176)
... 23 more
{code}
(tested with the last snapshot too)
The problem comes from jboss-as-cli that needs the JBOSS_HOME to be set in order to add
or remove modules. This is not a requirement for other commands such as deploy.
There are some points of confusion:
# JBOSS_HOME is set in .bashrc but IDEs do not read .bashrc, thereby it can work in some
cases but not in others;
# usually there are more than one installation or jboss-as-maven-plugin can download the
server;
# jbossHome config parameter is not take into account;
# what if I want to make operations on more the one server at the same time?
At the moment I solved by patching jboss-as-cli using a system property instead of
environment variable. I don't know how to solve without touching jboss-as-cli.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)