[jboss-jira] [JBoss JIRA] (WFLY-4490) Hard deployment using wildfly-maven-plugin

Hitesh Saxena (JIRA) issues at jboss.org
Wed Apr 8 05:02:19 EDT 2015


     [ https://issues.jboss.org/browse/WFLY-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hitesh Saxena updated WFLY-4490:
--------------------------------
    Fix Version/s:     (was: No Release)


> Hard deployment using wildfly-maven-plugin
> ------------------------------------------
>
>                 Key: WFLY-4490
>                 URL: https://issues.jboss.org/browse/WFLY-4490
>             Project: WildFly
>          Issue Type: Bug
>          Components: Build System
>    Affects Versions: 8.2.0.Final
>         Environment: OS- WIndows7 64Bit, Eclipse Luna Service Release 1(4.4.1), Maven 3.1.1
>            Reporter: Hitesh Saxena
>            Assignee: Paul Gier
>            Priority: Critical
>              Labels: jboss
>
> We are migrating from JBOSS6 to Wildfly8. We are a new issue which could not be found anywhere in forums,so posting this question here.
>  
> For hard deployment we were using the below configuration in pom.xml which actually copy and deploy ear file from ${JBOSS_HOME}/server/default/deploy directory of JBOSS6.
>  
> <plugin>	
> <groupId>org.codehaus.mojo</groupId>	
> <artifactId>jboss-maven-plugin</artifactId>	
> <executions>	
> <execution>	
> <id>deploy_ear</id>	
> <phase>pre-integration-test</phase>	
> <goals>	
> <goal>hard-deploy</goal>
> </goals>	
> <configuration>	
> <deploySubDir>./</deploySubDir>
> <fileName>target/${project.build.finalName.full}</fileName>
> <unpack>true</unpack>
> </configuration>	
> </execution>	
> </executions>	
> </plugin>	
>  
> But now as per wildlfy documents, we are using wildfly-maven-plugin to do the above and configured as below:
>  
> <plugin>
>                  <groupId>org.wildfly.plugins</groupId>
>                  <artifactId>wildfly-maven-plugin</artifactId>
> <executions>	
> <execution>	
> <id>deploy_ear</id>	
> <phase>package</phase>	
> <goals>	
> <goal>deploy</goal>
> </goals>	
> <configuration>	
> <skip>false</skip>
> <filename>test.ear</filename>
> <targetDir>${project_directory}\target</targetDir>
> <domain>standalone</domain>
> </configuration>	
> </execution>	
> </executions>	
> </plugin>
>  
> But this maven configuration deploys into ${JBOSS_HOME}/standalone/data/content and also make an entry into standalone-full-ha.xml file as below
>     <deployments>
>         <deployment name="test.ear" runtime-name="test.ear">
>             <content sha1="697809d5ebb7658fd7045dd6a8c41542cd3a0e02"/>
>         </deployment>
>     </deployments>
>  
> Ideally it should copy and deploy from into ${JBOSS_HOME}/standalone/deployments folder.
>  
> I tried to see the parameters from wildfly documents but could not get any parameter which can do the expected.
> reference: WildFly Maven Plugin - wildfly:deploy
>  
> Help will be highly appreciated as we are struck into this stage.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jboss-jira mailing list