You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Graeme Steyn (JIRA)" <ji...@codehaus.org> on 2008/06/23 01:54:26 UTC
[jira] Created: (MDEPLOY-81) NPE when deploying to remote repo
NPE when deploying to remote repo
---------------------------------
Key: MDEPLOY-81
URL: http://jira.codehaus.org/browse/MDEPLOY-81
Project: Maven 2.x Deploy Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: Windows XP SP 2 deploying to remote Solaris system running Archiva
Reporter: Graeme Steyn
When deploying multiple artifacts to a remote repository a NPE is generated if not all of the deploy commands have -DgeneratePom=true. For example:
mvn deploy:deploy-file -DgroupId=groupid -DartifactId=sampleArtifactId -Dversion=1.0.0 -Dpackaging=jar -DgeneratePom=true -Dfile=sample.jar -DrepositoryId=test dav:http://server/repository/test
mvn deploy:deploy-file -DgroupId=groupid -DartifactId=sampleArtifactId -Dversion=1.0.0 -Dpackaging=jar -DgeneratePom=false -Dfile=sample-javadoc.jar -Dclassifier=javadoc -DrepositoryId=test dav:http://server/repository/test
This results in the first command executing correctly and the second failing with:
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:919)
at org.apache.maven.project.artifact.ProjectArtifactMetadata.storeInLocalRepository(ProjectArtifactMetadata.java:86)
at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:437)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86)
at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:239)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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)
This is similar to NMAVEN-130.
--
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
[jira] Commented: (MDEPLOY-81) NPE when deploying to remote repo
Posted by "Marc Lustig (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154988#action_154988 ]
Marc Lustig commented on MDEPLOY-81:
------------------------------------
I get the same error, deploying from windows xp to Archiva 1.0.1
> NPE when deploying to remote repo
> ---------------------------------
>
> Key: MDEPLOY-81
> URL: http://jira.codehaus.org/browse/MDEPLOY-81
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: Windows XP SP 2 deploying to remote Solaris system running Archiva
> Reporter: Graeme Steyn
>
> When deploying multiple artifacts to a remote repository a NPE is generated if not all of the deploy commands have -DgeneratePom=true. For example:
> mvn deploy:deploy-file -DgroupId=groupid -DartifactId=sampleArtifactId -Dversion=1.0.0 -Dpackaging=jar -DgeneratePom=true -Dfile=sample.jar -DrepositoryId=test dav:http://server/repository/test
> mvn deploy:deploy-file -DgroupId=groupid -DartifactId=sampleArtifactId -Dversion=1.0.0 -Dpackaging=jar -DgeneratePom=false -Dfile=sample-javadoc.jar -Dclassifier=javadoc -DrepositoryId=test dav:http://server/repository/test
> This results in the first command executing correctly and the second failing with:
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:919)
> at org.apache.maven.project.artifact.ProjectArtifactMetadata.storeInLocalRepository(ProjectArtifactMetadata.java:86)
> at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:437)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86)
> at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:239)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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)
> This is similar to NMAVEN-130.
--
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
[jira] Closed: (MDEPLOY-81) NPE when deploying to remote repo
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MDEPLOY-81.
------------------------------------
Assignee: Benjamin Bentmann
Resolution: Duplicate
> NPE when deploying to remote repo
> ---------------------------------
>
> Key: MDEPLOY-81
> URL: http://jira.codehaus.org/browse/MDEPLOY-81
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: Windows XP SP 2 deploying to remote Solaris system running Archiva
> Reporter: Graeme Steyn
> Assignee: Benjamin Bentmann
>
> When deploying multiple artifacts to a remote repository a NPE is generated if not all of the deploy commands have -DgeneratePom=true. For example:
> mvn deploy:deploy-file -DgroupId=groupid -DartifactId=sampleArtifactId -Dversion=1.0.0 -Dpackaging=jar -DgeneratePom=true -Dfile=sample.jar -DrepositoryId=test dav:http://server/repository/test
> mvn deploy:deploy-file -DgroupId=groupid -DartifactId=sampleArtifactId -Dversion=1.0.0 -Dpackaging=jar -DgeneratePom=false -Dfile=sample-javadoc.jar -Dclassifier=javadoc -DrepositoryId=test dav:http://server/repository/test
> This results in the first command executing correctly and the second failing with:
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:919)
> at org.apache.maven.project.artifact.ProjectArtifactMetadata.storeInLocalRepository(ProjectArtifactMetadata.java:86)
> at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:437)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86)
> at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:239)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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)
> This is similar to NMAVEN-130.
--
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