[forge-issues] [JBoss JIRA] (FORGE-137) add war explode goal to scaffold pom

[Kevin Sapper (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637946#comment-12637946 ] 

Kevin Sapper commented on FORGE-137:
------------------------------------

Hi Lincoln,

I've a couple of ideas on how to solve this issue. The investigation below is focused on JBoss AS 7 only.
I copied the scenario approaches from the JBoss AS 7 deployments README.txt.

Within the pom.xml define variable for deployment mode, by default:
  - auto-deploy-zipped = "true" 
  - auto-deploy-exploded = "false"

h3. explode commands
  
*maven compile -Pexplode*
	- Scenario 1: Add new unzipped content and deploy it
{quote}
		1. cp -r target/example.war/ $AS/standalone/deployments
		2. (Manual mode only) touch $AS/standalone/deployments/example.war.dodeploy
{quote}
	- Scenario 2: Live replace portions of currently deployed unzipped content without redeploying
{quote}
		1. (Auto mode only) touch $AS/standalone/deployments/example.war.skipdeploy
		2. cp -r target/example.war/foo.html $AS/standalone/deployments/example.war
{quote}
One remark Scenario 2 only triggers if Scenario 1 has been executed first.

*maven compile -Pre-explode*
	- Scenario: Replace currently deployed zipped content with a new version and deploy it:
{quote}
		1. cp target/example.war/ $AS/standalone/deployments
		2. (Manual mode only) touch $AS/standalone/deployments/example.war.dodeploy		
{quote}

*maven clean -Punexplode*
        - Scenario: undeploy and remove unzipped content
{quote}
	    1. rm $AS/standalone/deployments/example.war.deployed
	    2. wait for $AS/standalone/deployments/example.war.undeployed file to appear
	    3. rm $AS/standalone/deployments/example.war
{quote}

h3. deploy commands
	
*maven package -Pdeploy*
	- Scenario: Add new zipped content and deploy it
{quote}
		1. cp -r target/example.war/ $AS/standalone/deployments
		2. (Manual mode only) touch $AS/standalone/deployments/example.war.dodeploy
{quote}
		
*maven package -Pre-deploy*
	- Scenario: Redeploy currently deployed content (i.e. bounce it with no content change):
{quote}
		1. touch $AS/standalone/deployments/example.war.dodeploy
{quote}
		
*maven clean -Pundeploy*
	- Scenario: undeploy and remove unzipped content
{quote}
		1. rm $AS/standalone/deployments/example.war.deployed
		2. wait for $AS/standalone/deployments/example.war.undeployed file to appear
		3. rm $AS/standalone/deployments/example.war
{quote}
		

I'm not sure whether the wait commands in unexplode and undeploy can be realized with maven. Therefore this might need a rework.

What do you think? Any questions or suggestions? Can you think of any pitfalls with this approach?

Regards//Kevin
                
> add war explode goal to scaffold pom
> ------------------------------------
>
>                 Key: FORGE-137
>                 URL: https://issues.jboss.org/browse/FORGE-137
>             Project: Forge
>          Issue Type: Enhancement
>          Components: Forge Build, Maven Integration
>         Environment: JBoss 6, Glassfish 3.1, JBoss 7?
>            Reporter: Kevin Sapper
>
> Hi Guys,
> One of the most compelling features about seam-gen is that after you've build the projects scaffold deploying and exploding to an application server just goes by calling an ant target. It really would be nice to have such a goal in the projects pom.xml after creating the scaffold and boilerplate code. Adding that functionality yourself really takes an awful lot of time. Especially with glassfish 3.1 I failed to accomplish that task.
> Best regards//Kevin

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira