[jboss-jira] [JBoss JIRA] (AS7-6092) Allow the CLI to deploy maven projects

[Nicholas DiPiazza (JIRA)]

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

Nicholas DiPiazza updated AS7-6092:
-----------------------------------

              Summary: Allow the CLI to deploy maven projects  (was: Allow deployment of exploded or unexploded maven projects directly.)
     Git Pull Request: https://github.com/jbossas/jboss-as/pull/3655
    Affects Version/s: 7.1.2.Final (EAP)
                           (was: 7.1.1.Final)
          Description: 
Allow users to deploy Maven projects directly from the CLI.

Create a new command "mavendeploy"

This will take a pom.xml for a war, ear or ejb project and will maven build, then deploy to the server using the DeployHandler.

First iteration of this would take same parameters as "deploy" except for one, --goals that specifies what goals to build the project with before deploying. (this makes it so you can clean before install, or just install, or call whatever goal that is needed to build the artifact).

Examples:

[standalone at localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml

[standalone at localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml --goals="clean install"

  was:
Allow users to deploy Maven projects directly.

In order to use this, must create Maven Settings configuration menu in jboss as7 console / properties files. Property settable from CLI.

Deployments allowed of type:

mavendeploy-mvn.xml
<mavendeploy>
|--- <pomLocation>
     |--- <scm>
          -- @scmhost, @port, @username, @password
     |--- <dir>
          -- @pomXmlFilePath
|--- <target>
     -- @artifactId
|--- <mavenOps>
     -- list of ops
When jboss sees this it automatially:

0) if scm, checkout to {configuration}/data/mvn/scmco/
1) mvn install project using opts specified {configuration}/data/mvn/{project}/target
2) deploy resource that maven just installed to target.

2) 


    
> Allow the CLI to deploy maven projects
> --------------------------------------
>
>                 Key: AS7-6092
>                 URL: https://issues.jboss.org/browse/AS7-6092
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Nicholas DiPiazza
>            Assignee: Jason Greene
>
> Allow users to deploy Maven projects directly from the CLI.
> Create a new command "mavendeploy"
> This will take a pom.xml for a war, ear or ejb project and will maven build, then deploy to the server using the DeployHandler.
> First iteration of this would take same parameters as "deploy" except for one, --goals that specifies what goals to build the project with before deploying. (this makes it so you can clean before install, or just install, or call whatever goal that is needed to build the artifact).
> Examples:
> [standalone at localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml
> [standalone at localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml --goals="clean install"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira