You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Aziz Joumady (JIRA)" <ji...@codehaus.org> on 2009/11/03 08:57:55 UTC
[jira] Commented: (MANTTASKS-123) Add option to generate pom upon
deployment.
[ 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