search

orctom / was-maven-plugin

Deploy artifact to one or more, local or remote WebSphere Application Server
Apache License 2.0
47 stars 29 forks source link

wasHome missing or invalid #6

Closed skHollywood closed 9 years ago

skHollywood commented 9 years ago

I am trying to run deploy goal, with the code in Readme.cmd, where wasHome is set. But it gives wasHome missing or invalid.

I have given value of was home as

C:\IBM\WebSphere\AppServer_1. 

                            <code> Starts Here </code>
                            <configuration>                                
                            <wasHome>${env.WAS_HOME}</wasHome>
                            <applicationName>${project.build.finalName}</applicationName>
                            <host>localhost</host>
                            <server>server1</server>
                            <node>Node01</node>
                            <virtualHost>default_host</virtualHost>

                        </configuration>
                          <code> Ends Here </code>

Any Idea?

using below command mvn -X com.orctom.mojo:was-maven-plugin:1.0.11:deploy

orctom commented 9 years ago

${env.WAS_HOME} reads from environment properties (it's Maven built-in mechanism), you have to restart your terminal after you set this property in system environment. Or you can try "hard code" the value as 

<wasHome>C:\IBM\WebSphere\AppServer_1</wasHome>
skHollywood commented 9 years ago

This is my configuration. I am using Version. 1.0.11.

com.orctom.mojo was-maven-plugin 1.0.11 default-cli install deploy ``` Test APP C:\IBM\WebSphere\AppServer_1 true 


Error:

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal com.orctom.mojo:was-maven-plugin:1.0.11:deploy (default-cli) on
project mmis-um-deploy: The parameters 'wasHome' for goal
com.orctom.mojo:was-maven-plugin:1.0.11:deploy are missing or invalid
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:220)
        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:116)
        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        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.PluginParameterException: The parameters
'wasHome' for goal com.orctom.mojo:was-maven-plugin:1.0.11:deploy are
missing or invalid
        at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:586)
        at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:539)
        at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        ... 19 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:

On Mon, Jun 29, 2015 at 8:50 PM, ORCTOM notifications@github.com wrote:

> ${env.WAS_HOME} reads from environment properties (it's Maven built-in
> mechanism), you have to restart your terminal after you set this property
> in system environment.
> Or you can try "hard code" the value as
> 
> <wasHome>C:\IBM\WebSphere\AppServer_1</wasHome>
> 
> —
> Reply to this email directly or view it on GitHub
> https://github.com/orctom/was-maven-plugin/issues/6#issuecomment-116910342
> .
skHollywood commented 9 years ago

Typo Tested both with and . same error.

C:\IBM\WebSphere\AppServer_1

Thanks, Siva

On Wed, Jul 1, 2015 at 11:17 AM, Siva kumar kumar.nsk@gmail.com wrote:

This is my configuration. I am using Version. 1.0.11.

com.orctom.mojo was-maven-plugin 1.0.11 default-cli install deploy ``` Test APP C:\IBM\WebSphere\AppServer_1 true 


Error:

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal com.orctom.mojo:was-maven-plugin:1.0.11:deploy (default-cli) on
project mmis-um-deploy: The parameters 'wasHome' for goal
com.orctom.mojo:was-maven-plugin:1.0.11:deploy are missing or invalid
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:220)
        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:116)
        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        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.PluginParameterException: The
parameters 'wasHome' for goal
com.orctom.mojo:was-maven-plugin:1.0.11:deploy are missing or invalid
        at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:586)
        at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:539)
        at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        ... 19 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:

On Mon, Jun 29, 2015 at 8:50 PM, ORCTOM notifications@github.com wrote:

> ${env.WAS_HOME} reads from environment properties (it's Maven built-in
> mechanism), you have to restart your terminal after you set this property
> in system environment.
> Or you can try "hard code" the value as
> 
> <wasHome>C:\IBM\WebSphere\AppServer_1</wasHome>
> 
> —
> Reply to this email directly or view it on GitHub
> https://github.com/orctom/was-maven-plugin/issues/6#issuecomment-116910342
> .
skHollywood commented 9 years ago

Dom is coming as below. I dont see .. should it have wasHome?

<?xml version="1.0" encoding="UTF-8"?>

Thanks, Siva

On Wed, Jul 1, 2015 at 11:24 AM, Siva kumar kumar.nsk@gmail.com wrote:

Typo Tested both with and . same error.

C:\IBM\WebSphere\AppServer_1

Thanks, Siva

On Wed, Jul 1, 2015 at 11:17 AM, Siva kumar kumar.nsk@gmail.com wrote:

This is my configuration. I am using Version. 1.0.11.

com.orctom.mojo was-maven-plugin 1.0.11 default-cli install deploy ``` Test APP C:\IBM\WebSphere\AppServer_1 true 


Error:

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal com.orctom.mojo:was-maven-plugin:1.0.11:deploy (default-cli) on
project mmis-um-deploy: The parameters 'wasHome' for goal
com.orctom.mojo:was-maven-plugin:1.0.11:deploy are missing or invalid
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:220)
        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:116)
        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        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.PluginParameterException: The
parameters 'wasHome' for goal
com.orctom.mojo:was-maven-plugin:1.0.11:deploy are missing or invalid
        at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:586)
        at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:539)
        at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        ... 19 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:

On Mon, Jun 29, 2015 at 8:50 PM, ORCTOM notifications@github.com wrote:

> ${env.WAS_HOME} reads from environment properties (it's Maven built-in
> mechanism), you have to restart your terminal after you set this property
> in system environment.
> Or you can try "hard code" the value as
> 
> <wasHome>C:\IBM\WebSphere\AppServer_1</wasHome>
> 
> —
> Reply to this email directly or view it on GitHub
> https://github.com/orctom/was-maven-plugin/issues/6#issuecomment-116910342
> .
orctom commented 9 years ago

Please don't try <wasHome1> any more, never said supporting that param. It's always <wasHome>. And yes you have to have <wasHome> in your pom (as an emphasis).

Paste your full pom here if possible, (replace information that you don't want to expose with 'xxx` or something if you need)