maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uldis Karlovs-Karlovskis (JIRA)" <>
Subject [jira] (MNG-5278) deploy:deploy does not work for only Deploying artifact to Maven Remote repo
Date Thu, 06 Sep 2012 06:41:21 GMT


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?

> deploy:deploy does not work for only Deploying artifact to Maven Remote repo
> ----------------------------------------------------------------------------
>                 Key: MNG-5278
>                 URL:
>             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(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>         at org.apache.maven.DefaultMaven.doExecute(
>         at org.apache.maven.DefaultMaven.execute(
>         at org.apache.maven.cli.MavenCli.main(
>         at org.apache.maven.cli.compat.CompatibleMain.main(
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>         at java.lang.reflect.Method.invoke(
>         at org.codehaus.classworlds.Launcher.launchEnhanced(
>         at org.codehaus.classworlds.Launcher.launch(
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(
>         at org.codehaus.classworlds.Launcher.main(
> 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(
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message