[
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
