You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2009/11/26 00:21:55 UTC

[jira] Closed: (MANTTASKS-123) Add option to generate pom upon deployment.

     [ 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