[jira] Created: (MNG-3851) Add option to generate pom upon deployment.

Add option to generate pom upon deployment.
-------------------------------------------

                 Key: MNG-3851
                 URL: http://jira.codehaus.org/browse/MNG-3851
             Project: Maven 2
          Issue Type: New Feature
          Components: Ant tasks
            Reporter: Paul Gier


The current ant install and deploy tasks require an existing pom file.  There should be a way to specify a groupId, artifactId, and version and have the ant taks automatically generate a simple pom.  This should work like the deploy:deploy-file goal.

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

       

    [ http://jira.codehaus.org/browse/MANTTASKS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196110#action_196110 ]

Aziz Joumady commented on MANTTASKS-123:
----------------------------------------

Hi,

Why don't you use/create an archetype to generate, first, your project architecture (pom.xml, src/main/java, etc.)
http://maven.apache.org/plugins/maven-archetype-plugin/

Kind regards,

Aziz

> Add option to generate pom upon deployment.
> -------------------------------------------
>
>                 Key: MANTTASKS-123
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-123
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>            Reporter: Paul Gier
>
> The current ant install and deploy tasks require an existing pom file.  There should be a way to specify a groupId, artifactId, and version and have the ant taks automatically generate a simple pom.  This should work like the deploy:deploy-file goal.

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

       

    [ http://jira.codehaus.org/browse/MANTTASKS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196125#action_196125 ]

Paul Gier commented on MANTTASKS-123:
-------------------------------------

The project is not using Maven for the build.  The point of the maven ant tasks is to allow an Ant build to access some of the features of Maven including deploying to a repository.  Since the build is using Ant, there are several jars that do not have POM files.  It would be good if there was an easy way to generate the POM file at some point before or during deployment.

> Add option to generate pom upon deployment.
> -------------------------------------------
>
>                 Key: MANTTASKS-123
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-123
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>            Reporter: Paul Gier
>
> The current ant install and deploy tasks require an existing pom file.  There should be a way to specify a groupId, artifactId, and version and have the ant taks automatically generate a simple pom.  This should work like the deploy:deploy-file goal.

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

       

    [ http://jira.codehaus.org/browse/MANTTASKS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196953#action_196953 ]

Aziz Joumady commented on MANTTASKS-123:
----------------------------------------

Hi Paul,

The Install plugin enable to generate a pom file.
Since an installation is a step before the deployment, if you explicitly install and then  deploy your jars, does it resolve your problem ?

{code}
mvn install:install-file  -Dfile=path-to-your-artifact-jar \
                          -DgroupId=your.groupId \
                          -DartifactId=your-artifactId \
                          -Dversion=version \
                          -Dpackaging=jar \
                          -DgeneratePom=true
{code}
http://maven.apache.org/plugins/maven-install-plugin/examples/generic-pom-generation.html

Regards,

Aziz

> Add option to generate pom upon deployment.
> -------------------------------------------
>
>                 Key: MANTTASKS-123
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-123
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>            Reporter: Paul Gier
>
> The current ant install and deploy tasks require an existing pom file.  There should be a way to specify a groupId, artifactId, and version and have the ant taks automatically generate a simple pom.  This should work like the deploy:deploy-file goal.

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

       

    [ http://jira.codehaus.org/browse/MANTTASKS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198572#action_198572 ]

Paul Gier commented on MANTTASKS-123:
-------------------------------------

Aziz, any solution that requires "mvn" is not in applicable to the maven ant tasks.  This is for an Ant build, so it is not safe to assume that Maven is even installed on the system.  The goal is to generate a pom using only Ant and the jar that contains the maven ant tasks.

> Add option to generate pom upon deployment.
> -------------------------------------------
>
>                 Key: MANTTASKS-123
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-123
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>            Reporter: Paul Gier
>
> The current ant install and deploy tasks require an existing pom file.  There should be a way to specify a groupId, artifactId, and version and have the ant taks automatically generate a simple pom.  This should work like the deploy:deploy-file goal.

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

       

     [ http://jira.codehaus.org/browse/MANTTASKS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier closed MANTTASKS-123.
-------------------------------

    Resolution: Won't Fix

This is better handled by the new writePom task in MANTTASKS-168.

> Add option to generate pom upon deployment.
> -------------------------------------------
>
>                 Key: MANTTASKS-123
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-123
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>            Reporter: Paul Gier
>
> The current ant install and deploy tasks require an existing pom file.  There should be a way to specify a groupId, artifactId, and version and have the ant taks automatically generate a simple pom.  This should work like the deploy:deploy-file goal.

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