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 2014/04/30 19:02:10 UTC
[jira] (MDEPLOY-180) deploy:deploy with
maven-deploy-plugin:2.7:deploy
[ https://jira.codehaus.org/browse/MDEPLOY-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte moved MNG-5627 to MDEPLOY-180:
---------------------------------------------
Complexity: (was: Intermediate)
Affects Version/s: (was: 3.1.1)
2.7
Key: MDEPLOY-180 (was: MNG-5627)
Project: Maven Deploy Plugin (was: Maven 2 & 3)
> deploy:deploy with maven-deploy-plugin:2.7:deploy
> -------------------------------------------------
>
> Key: MDEPLOY-180
> URL: https://jira.codehaus.org/browse/MDEPLOY-180
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Affects Versions: 2.7
> Environment: Window 7 64bit + Eclipse Kepler
> Reporter: Martin Spamer
> Priority: Critical
>
> Upgrade to org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy results in critical failure when issuing deploy:deploy.
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-cli) on project who-test-core: The packaging for this project did not assign a file to the build artifact -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-cli) on project who-test-core: The packaging for this project did not assign a file to the build artifact
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:46)
> 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:180)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> [ERROR]
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)