Hi Nafter, the itblast plugin uses cargo behind the scene to start your war and then uses the surefire plugin to run your tests. You don't need to declare a separate instance of cargo in your pom.
It looks like however that you are using an already running instance of cargo to deploy/undeploy your war to. The it blast doesn't support this kind of configuration. It will actually download each container you specify, install and start them locally deploying your webapp. Hope this make sense. SaM On Sun, Apr 12, 2009 at 8:13 PM, Nafter <[email protected]> wrote: > > I use cargo to undeploy and to deploy my WAR to JBoss 4.2.3. This is working > ok. > Now I want to use the itblast plugin to start my integration tests on the > same JBoss instance. > This JBoss instance is already running with the lastest WAR because of the > cargo deploy execution which has been executed during the > pre-integration-test phase. > > However when itblast executes it tries to start JBoss again instead of > pointing to the already running instance of JBoss. I did instruct the > itblast plugin about the correct httpport and rmiport to use. > > Can somebody please help me out? > > Here is a snippet of my pom: > <profile> > <id>deploy_war2</id> > <activation> > <property> > <name>deploy2</name> > </property> > </activation> > <build> > <plugins> > <plugin> > <groupId>org.codehaus.cargo</groupId> > <artifactId>cargo-maven2-plugin</artifactId> > <version>1.0-beta-2</version> > <configuration> > > <!-- Container configuration --> > <container> > <containerId>jboss42x</containerId> > > <home>c:/_composer/_composer5/jboss-4.2.3.GA_Composer</home> > </container> > > <!-- Configuration to use with the container --> > <configuration> > <type>standalone</type> > > <home>c:/_composer/_composer5/jboss-4.2.3.GA_Composer/server/default</home> > <properties> > <cargo.rmi.port>18080</cargo.rmi.port> > </properties> > </configuration> > > <!-- Deployer configuration --> > <deployer> > <deployables> > <deployable> > > <groupId>${pview.group}</groupId> > <artifactId>PV_Web</artifactId> > <type>war</type> > > <pingURL>http://localhost:18080/PV_Web-${pview.version}/composer/login.jsp</pingURL> > > <pingTimeout>100000</pingTimeout> > </deployable> > </deployables> > </deployer> > </configuration> > <executions> > <execution> > <id>deploy_to_jboss</id> > <phase>pre-integration-test</phase> > <goals> > <goal>undeploy</goal> > <goal>deploy</goal> > </goals> > </execution> > </executions> > </plugin> > <plugin> > <groupId>org.twdata.maven</groupId> > <artifactId>maven-itblast-plugin</artifactId> > <version>0.5</version> > <executions> > <execution> > <phase>integration-test</phase> > <goals> > <goal>execute</goal> > </goals> > <configuration> > <containers>jboss42x</containers> > > <httpPort>18080</httpPort> > > <rmiPort>11098</rmiPort> > > <functionalTestPattern>**/TestDateUtility.java</functionalTestPattern> > <includes> > > <include>**/TestDateUtility.java</include> > </includes> > </configuration> > </execution> > </executions> > </plugin> > </plugins> > </build> > </profile> > > > > Here is a snippet of my output: > [INFO] [cargo:undeploy {execution: deploy_to_jboss}] > [INFO] [talledLocalContainer] Parsed JBoss version = [4.2.3] > [INFO] [stalledLocalDeployer] Undeploying > [c:/_composer/_composer5/jboss-4.2.3.GA_Composer/server/default/deploy/PV_Web-5.0.0.war]... > [INFO] [cargo:deploy {execution: deploy_to_jboss}] > [INFO] [stalledLocalDeployer] Deploying > [c:\_composer\_build\war\PV_Web-5.0.0.war] to > [c:/_composer/_composer5/jboss-4.2.3.GA_Composer/server/default/deploy]... > [INFO] [itblast:execute {execution: default}] > [INFO] Running integration tests on the jboss42x container on ports 18080 > (http) and 11098 (rmi) > [INFO] [cargo:start {execution: virtual-execution}] > [INFO] [neLocalConfiguration] Configuring JBoss using the [default] server > configuration > [INFO] [talledLocalContainer] Parsed JBoss version = [4.2.3] > [INFO] [talledLocalContainer] JBoss 4.2.3 starting... WHY WHY it is already > RUNNING !! > [INFO] [talledLocalContainer] 12:00:34,836 INFO [Server] Starting JBoss (MX > MicroKernel)... > [INFO] [talledLocalContainer] 12:00:34,852 INFO [Server] Release ID: JBoss > [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417) > [INFO] [talledLocalContainer] 12:00:34,852 INFO [Server] Home Dir: > C:\_composer\_composer5\jboss-4.2.3.GA_Composer > [INFO] [talledLocalContainer] 12:00:34,852 INFO [Server] Home URL: > file:/c:/_composer/_composer5/jboss-4.2.3.GA_Composer/ > [INFO] [talledLocalContainer] 12:00:34,852 INFO [Server] Patch URL: null > [INFO] [talledLocalContainer] 12:00:34,852 INFO [Server] Server Name: > default > [INFO] [talledLocalContainer] 12:00:34,852 INFO [Server] Server Home Dir: > C:\_composer\_build\war\jboss42x\server > [INFO] [talledLocalContainer] 12:00:34,852 INFO [Server] Server Home URL: > file:/c:/_composer/_build/war/jboss42x/server/ > [INFO] [talledLocalContainer] 12:00:34,852 INFO [Server] Server Log Dir: > C:\_composer\_build\war\jboss42x\server\log > [INFO] [talledLocalContainer] 12:00:34,852 INFO [Server] Server Temp Dir: > C:\_composer\_build\war\jboss42x\server\tmp > [INFO] [talledLocalContainer] 12:00:34,867 INFO [Server] Root Deployment > Filename: jboss-service.xml > [INFO] [talledLocalContainer] 12:00:35,274 INFO [ServerInfo] Java version: > 1.6.0_12,Sun Microsystems Inc. > [INFO] [talledLocalContainer] 12:00:35,274 INFO [ServerInfo] Java VM: Java > HotSpot(TM) Client VM 11.2-b01,Sun Microsystems Inc. > [INFO] [talledLocalContainer] 12:00:35,274 INFO [ServerInfo] OS-System: > Windows Server 2008 6.0,x86 > [INFO] [talledLocalContainer] 12:00:35,649 INFO [Server] Core system > initialized > [INFO] [talledLocalContainer] 12:00:37,930 INFO [ServiceBindingManager] > Initializing store > [INFO] [talledLocalContainer] 12:00:37,930 INFO [ServiceBindingManager] > Using StoreURL: > file:/C:/_composer/_build/war/jboss42x/server/conf/cargo-binding.xml > [INFO] [talledLocalContainer] 12:00:38,696 INFO [WebService] Using RMI > server codebase: http://127.0.0.1:8083/ > [INFO] [talledLocalContainer] 12:00:38,711 INFO > [Log4jService$URLWatchTimerTask] Configuring from URL: > resource:jboss-log4j.xml > [INFO] [talledLocalContainer] 12:00:38,992 WARN [ServiceController] Problem > starting service jboss:service=WebService > [INFO] [talledLocalContainer] java.lang.Exception: Port 8083 already in use. > [INFO] [talledLocalContainer] at > org.jboss.web.WebServer.start(WebServer.java:233) > [INFO] [talledLocalContainer] at > org.jboss.web.WebService.startService(WebService.java:322) > [INFO] [talledLocalContainer] at > org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) > [INFO] [talledLocalContainer] at > org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) > [INFO] [talledLocalContainer] at > sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > [INFO] [talledLocalContainer] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [INFO] [talledLocalContainer] at > java.lang.reflect.Method.invoke(Method.java:597) > [INFO] [talledLocalContainer] at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > [INFO] [talledLocalContainer] at > org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > [INFO] [talledLocalContainer] at > org.jboss.mx.server.Invocation.invoke(Invocation.java:86) > [INFO] [talledLocalContainer] at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > -- > View this message in context: > http://www.nabble.com/itblast-plugin-is-starting-JBoss-again-but-this-is-already-running-tp23009792p23009792.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
