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. Regards, David K Rohnny Moland wrote: > > On Fri, Mar 21, 2008 at 3:12 AM, David J. M. Karlsen > <[EMAIL PROTECTED]> wrote: >> Hi folks! >> >> The was6-maven-plugin has just graduated, and released as version >> 1.0-alpha-1. >> >> The plugin can be used to start and stop websphere 6.1 containers (ND or >> standalone installations) and applications, >> generate WAS specific bindings, generate EJB deployment code (stubs), >> and run arbitrary scripts (JCAL/Jython) against WAS. >> It's implemented as a wrapper around ws_ant - WAS's own wrapper around >> ant and WAS ant tasks, which ensures the correct setup of environment. > > Thanks for this, David. I tried it now, and I can start and stop the > server, but have some problems installing ear files into websphere via > the wsInstallApp goal. Some of the log output; > > INFO] The ' characters around the executable and arguments are > [INFO] not part of the command. > [INFO] [wsadmin] WASX7357I: By request, this scripting client is not > connected to any server process. Certain configuration and application > operations will be available in local mode. > [INFO] [wsadmin] WASX7017E: Exception received while running file > "/tmp/wsant46650jacl"; exception information: > com.ibm.ws.scripting.ScriptingException: WASX7280E: An application > with name "cargoear" does not exist. > [INFO] > [ERROR] > [ERROR] BUILD FAILED > [ERROR] > /usr/local/src/testcargo/testcargo/target/was6plugin/was6plugin-build.xml:23: > Java returned: 105 > > ..and my configuration; > > <configuration> > > <wasHome>/usr/local/WebSphere/AppServer</wasHome> > <host>rohnny-laptop</host> > <applicationName>cargoear</applicationName> > <username>system</username> > <password>...</password> > <profileName>AppSrv02</profileName> > > <earFile>/usr/local/src/testcargo/cargoear/target/cargoear.ear</earFile> > <verbose>true</verbose> > </configuration> > > I am also curious why you want to create your own plugin for > websphere, instead of patching up cargo? As you know cargo is a nice > framework for this, and it shouldnt be much work integrating websphere > with cargo; I even think it is 90% done already. > > Kind regards, > Rohnny > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > ----- http://www.davidkarlsen.com -- View this message in context: http://www.nabble.com/-ANN--was6-maven-plugin-1.0-alpha-1-release-tp16192936p16237822.html Sent from the mojo - user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
