On Sun, Mar 23, 2008 at 5:44 PM, davidkarlsen <[EMAIL PROTECTED]> wrote:
>
> Hei/hi! :-)
>
> See the
>
> http://mojo.codehaus.org/was6-maven-plugin/installApp-mojo.html#updateExisting
> option.
> The first time you install the application this needs to be false.
> On subsequent runs leaving it to true (the default) will update the existing
> installed application (which will merge the settings). You can provide this
> option on the CLI by using -Dwas6.updateExisting=false.
>
> The approach in this plugin is a little different from cargo (cargo is very
> centered around launching ant-tasks). As websphere has a very complex
> classpath to resemble, which also may change between installation types -
> this plugin is centered around launching ws_ant commandlines, and besides
> this the main focus was creating a m2 plugin (Cargo is a API + m1, ant and
> m2 plugins). Also by having this rather narrow focus allows for more rapid
> releases.
>
> Besides this it also has some other goals - the wsBindings, ejbdeploy and
> wsAdmin which are websphere propietary.
>
> That said - [parts of] it may very well be refactored and put into cargo in
> the future.
Yes, after looking closer at the plugin, I agree. :) I actually think
its difficult to do all the stuff this plugin does with cargo because
it wraps the wsadmin task. For the record, I paste in the
configuration that worked for me. It starts, stops the server, deploys
and undeploys an ear file.
<profile>
<id>was6x</id>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>was6-maven-plugin</artifactId>
<executions>
<execution>
<id>start-server</id>
<phase>pre-integration-test</phase>
<goals>
<goal>wsStartServer</goal>
<goal>wsDefaultBindings</goal>
<goal>installApp</goal>
</goals>
</execution>
<execution>
<id>stop-server</id>
<phase>post-integration-test</phase>
<goals>
<goal>wsUninstallApp</goal>
<goal>wsAdmin</goal>
</goals>
</execution>
</executions>
<configuration>
<wasHome>/usr/local/WebSphere/AppServer</wasHome>
<host>rohnny-laptop</host>
<applicationName>cargoear</applicationName>
<username>system</username>
<user>system</user>
<password>...</password>
<profileName>AppSrv02</profileName>
<earFile>/usr/local/src/testcargo/cargoear/target/cargoear.ear</earFile>
<verbose>true</verbose>
<updateExisting>false</updateExisting>
<strategy>${basedir}/src/test/resources/bindings.xml</strategy>
<command>$AdminControl stopServer server1</command>
</configuration>
</plugin>
</plugins>
</build>
</profile>
What I couldnt get working was to set the properties tag in the
configuration. Maybe I just didnt understand it..but I would like to
set jvm arguments like heap size and I also need to set a system
property that my application uses. How should this file look like?
Thanks,
Rohnny
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email