You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2013/03/09 21:07:52 UTC
[jira] (MDEPLOY-158) deploy:deploy does not work for only Deploying
artifact to Maven Remote repo
[ https://jira.codehaus.org/browse/MDEPLOY-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte moved MNG-5278 to MDEPLOY-158:
---------------------------------------------
Complexity: (was: Intermediate)
Affects Version/s: (was: 3.0.3)
(was: 2.2.1)
Key: MDEPLOY-158 (was: MNG-5278)
Project: Maven 2.x and 3.x Deploy Plugin (was: Maven 2 & 3)
> deploy:deploy does not work for only Deploying artifact to Maven Remote repo
> ----------------------------------------------------------------------------
>
> Key: MDEPLOY-158
> URL: https://jira.codehaus.org/browse/MDEPLOY-158
> Project: Maven 2.x and 3.x Deploy Plugin
> Issue Type: Bug
> Environment: Windows
> Reporter: Himanshu Goyal
> Priority: Critical
> Attachments: mvnDeployException.jpeg
>
>
> I did a mvn install in the first place in order to generate artifact for my maven project.
> As a second step I wanted to make a decision to only "deploy" the generated artifact to the remote repo using
> "mvn deploy:deploy" command
> Since the artifact is already been compiled, created inside target folders, there should not be any need to force a developer to rerun everything if we wish to only upload the artifact to remote repo.
> When we execute "mvn deploy:deploy", it gives the following error:
> org.apache.maven.lifecycle.LifecycleExecutionException: The packaging for this project did not assign a file to the build artifact
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: The packaging for this project did not assign a file to the build artifact
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:182)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
--
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