[jboss-jira] [JBoss JIRA] Commented: (JBBUILD-478) Create "deploy", "undeploy" Mojos for maven-jboss-as-control-plugin

[Antony Stubbs (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBBUILD-478?page=comments#action_12420079 ] 
            
Antony Stubbs commented on JBBUILD-478:
---------------------------------------

Another feature that should also be added is checking what packaging type the project is - for example a MojoFailureException if the packaging type is pom.

The other thing I noticed is that the JbossAsControlCreateConfigurationMojo doesn't seem to perform a delta copy as ALR has mentioned in places, but instead copies the entire directory every time and overwrites existing files. Is this a feature worth pursuing? It took quite a long time (at least 60 seconds) copying the config directory on every invoke for me - i.e. it appears worth it to me.

It also looks like it might be worth abstracting out the other common properties / functions from the mojo's into a super class, as I have done with JbossAbstractDeploymentMojo. Maven still appears to set all the properties etc correctly and it gets rid of a lot of duplicate code.

> Create "deploy", "undeploy" Mojos for maven-jboss-as-control-plugin
> -------------------------------------------------------------------
>
>                 Key: JBBUILD-478
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-478
>             Project: JBoss Build System
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>         Attachments: jboss-server-manager.patch, maven-jboss-as-control-example alternate pom.patch, maven-jboss-as-control-example.patch, maven-jboss-plugins-aggregator.patch
>
>
> The JBoss AS Control Plugin currently has Mojos for "createConfiguration", "start", and "stop".  We need to add both a "deploy" and "undeploy" Mojo which delegates to congruent functionality from jboss-server-manager.
> Existing Mojos:
> http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk/maven-jboss-as-control-plugin/src/main/java/org/jboss/maven/plugins/as/control/mojo/
> Root Checkout Location:
> http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk
> Server Manager (Powers the maven-jboss-as-common delegates):
> http://anonsvn.jboss.org/repos/jbossas/projects/server-manager/trunk/
> After these are created, configuration to use them should be added to the "maven-jboss-as-control-example" project, following examples already in place in the POM.  This is the self-documenting usage project which may also prove its validity.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira