Hi, I have few queries regarding the CI with luntbuild and Maven 1.1.b2 :
1) As was mentioned earlier by Vincent in my previous mail, the CI Tool, luntbuild, doesn't allow to keep the jboss container in running state with the mavel goal, cargo:startAndWait.So Is there any way such that luntbuild can start the container, deploy the ear. After deployment we can access the site. 2) Is it possible that the luntbuild and the jboss app server are in two different machines and we can acheive the same as in 1. 3) I can see that with cargo:startAndWait, luntbuild deploys the ear in the standalone configuration's tmp folder. Can't it deploy to the <jboss-home-dir>/server/default/deploy folder. In the later case we can keep the jboss container started and after luntbuild deploys in the default configuration, we can access the site. 4) If luntbuild doesn't allow cargo:startAndWait goal to keep the server in running mode, can we use the cargo:start goal instead. 5) Does Maven 1.1 b2 or Maven 2 support existing configuration? 6) Does Maven 2 help answer the above mentioned queries ? -- Warm Regards Manisha Sur
