AW: WAS6-plugin error

2008-05-21 Thread Lustig, Marc (Allianz Deutschland AG)
ty for the hint, but this won't help as we want to use the was6-plugin for 
Continuous Integration (with Continuum), i. e. the deployment package will be 
build by Continuum in an arbitrary tmp-file, hence we don't no the path in 
advance.

The was6-plugin should either pick the deployment package up from the 
target-dir, or alternatively, from the local maven repo.

Is either of this possible?


-Ursprüngliche Nachricht-
Von: Tim Kettler [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 21. Mai 2008 10:58
An: Maven Users List
Betreff: Re: WAS6-plugin error

Hi,

I've never used the was-plugin, but looking at the documentation and 
source code, it seems that the default assumption of the 'installAp' 
goal is that it is running as part of a maven build.

The 'earFile' parameter is automatically populated with the current 
projects main artifact [1], which is obviously not available when you 
invoke the goal standalone. What should work, is that you specify the 
ear file explicitly on the command line:

   mvn -Dwas6.earFile=/path/to/my.ear  was6:installApp

Hope this helps
-Tim

[1] http://mojo.codehaus.org/was6-maven-plugin/installApp-mojo.html#earFile

Lustig, Marc (Allianz Deutschland AG) schrieb:
 mvn package
 ..
 [INFO] BUILD SUCCESSFUL
 ..
 mvn was6:installApp
 ...
 [ERROR] FATAL ERROR
 [INFO]
 
 [INFO] null
 [INFO]
 
 [INFO] Trace
 java.lang.NullPointerException
 at
 org.codehaus.mojo.was6.WsInstallAppMojo.configureBuildScript(WsInstallAp
 pMojo.java:54)
 
 
 the pom.xml look like this:
 plugin
   groupIdorg.codehaus.mojo/groupId
   
 artifactIdwas6-maven-plugin/artifactId
   version1.0-alpha-2/version
   executions
   execution
   
 idintegration-test/id
   
 phaseintegration-test/phase
   goals
   
 goalwsStopServer/goal
   
 goalinstallApp/goal
   
 goalwsStartServer/goal
 /goals
   /execution
   /executions
   configuration
   
 wasHomec:/Programme/ibm/SDP70/runtimes/base_v61/wasHome
   hostlocalhost/host
   usernameadmin/username
   password/password
   !--
   
 targetClusternameOfCluster/targetCluster
   --
   
 profileNameAppSrv01/profileName
   !-- remember to import
 certificate from remote site when deploying to a site with security
 activated --
   conntypeSOAP/conntype
   port8880/port
   verbosetrue/verbose
 !-- need to be false first time it's
 deployed to a server -- 
   
 updateExistingfalse/updateExisting
   /configuration
   /plugin
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: AW: WAS6-plugin error

2008-05-21 Thread Tim Kettler
I don't think this is possible. Why isn't just building the project (in 
Continuum) with 'mvn post-integration-test' or something like that an 
option?


Lustig, Marc (Allianz Deutschland AG) schrieb:

ty for the hint, but this won't help as we want to use the was6-plugin for 
Continuous Integration (with Continuum), i. e. the deployment package will be 
build by Continuum in an arbitrary tmp-file, hence we don't no the path in 
advance.

The was6-plugin should either pick the deployment package up from the 
target-dir, or alternatively, from the local maven repo.

Is either of this possible?


-Ursprüngliche Nachricht-
Von: Tim Kettler [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 21. Mai 2008 10:58

An: Maven Users List
Betreff: Re: WAS6-plugin error

Hi,

I've never used the was-plugin, but looking at the documentation and 
source code, it seems that the default assumption of the 'installAp' 
goal is that it is running as part of a maven build.


The 'earFile' parameter is automatically populated with the current 
projects main artifact [1], which is obviously not available when you 
invoke the goal standalone. What should work, is that you specify the 
ear file explicitly on the command line:


   mvn -Dwas6.earFile=/path/to/my.ear  was6:installApp

Hope this helps
-Tim

[1] http://mojo.codehaus.org/was6-maven-plugin/installApp-mojo.html#earFile

Lustig, Marc (Allianz Deutschland AG) schrieb:

mvn package

..
[INFO] BUILD SUCCESSFUL
..

mvn was6:installApp

...
[ERROR] FATAL ERROR
[INFO]

[INFO] null
[INFO]

[INFO] Trace
java.lang.NullPointerException
at
org.codehaus.mojo.was6.WsInstallAppMojo.configureBuildScript(WsInstallAp
pMojo.java:54)


the pom.xml look like this:
plugin
groupIdorg.codehaus.mojo/groupId

artifactIdwas6-maven-plugin/artifactId
version1.0-alpha-2/version
executions
execution

idintegration-test/id

phaseintegration-test/phase
goals

goalwsStopServer/goal

goalinstallApp/goal

goalwsStartServer/goal
  /goals
/execution
/executions
configuration

wasHomec:/Programme/ibm/SDP70/runtimes/base_v61/wasHome
hostlocalhost/host
usernameadmin/username
password/password
!--

targetClusternameOfCluster/targetCluster
--

profileNameAppSrv01/profileName
!-- remember to import
certificate from remote site when deploying to a site with security
activated --
conntypeSOAP/conntype
port8880/port
verbosetrue/verbose
  !-- need to be false first time it's
deployed to a server -- 
	

updateExistingfalse/updateExisting
/configuration
/plugin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]