[jira] (MNG-5278) deploy:deploy does not work for only Deploying artifact to Maven Remote repo

["Uldis Karlovs-Karlovskis (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307834#comment-307834 ] 

Uldis Karlovs-Karlovskis commented on MNG-5278:
-----------------------------------------------

Hi all,

I see no one even tried to help this guy. I'm having exactly the same problem with any version of Maven. What I need to achieve is quite simple:
1) build artifact with mvn package
2) deploy artifact to repo with install to local repository

I'm doing it from CI and I need to do it in at least two steps. What properties should I specify or which required goals to run to get deploy:deploy working?

Regards
Uldis
                
> deploy:deploy does not work for only Deploying artifact to Maven Remote repo
> ----------------------------------------------------------------------------
>
>                 Key: MNG-5278
>                 URL: https://jira.codehaus.org/browse/MNG-5278
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 2.2.1, 3.0.3
>         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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira