You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mauritz Lovgren (JIRA)" <ji...@codehaus.org> on 2006/05/09 09:55:42 UTC
[jira] Created: (MECLIPSE-105) deploy gives NPE in wagon-ftp
deploy gives NPE in wagon-ftp
-----------------------------
Key: MECLIPSE-105
URL: http://jira.codehaus.org/browse/MECLIPSE-105
Project: Maven 2.x Eclipse Plugin
Type: Bug
Environment: Win 2000 Pro, Sun JDK 1.5.0_06, Maven 2.0.4, Eclipse 3.2 RC2, org.maven.ide.eclipse_0.0.7
Reporter: Mauritz Lovgren
Attachments: command.log, eclipse.log
When running deploy goal for pom containing ftp deployment, the following NPE is thrown just as files are starting to push to ftp server:
[INFO] deploy:deploy
[DEBUG] not adding permissions to wagon connection
java.lang.NullPointerException
at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:127)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:178)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:131)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382)
at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
This problem does not occur when running mvn deploy in command prompt.
I notice a small difference in debug output from Eclipse / command prompt that might be something?
Eclipse:
[DEBUG] Found 0 components to load on start
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level settings from: 'C:\dev\ws\ic-sntdispatcher\conf\settings.xml'
[DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\t539537\.m2\settings.xml'
[DEBUG] Profile with id: 'default-profile' has been explicitly activated.
[DEBUG] Profile with id: 'default-profile' has been explicitly activated.
Command prompt:
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\maven-2.0.2\conf\plugin-registry.xml'
[INFO] Scanning for projects...
I have defined ftp server credentials in user home ./m2/settings.xml. Could it be that these credentials are not found when running in Eclipse Maven2 plugin?
This is not a critical error for me, as I can just deploy using command prompt, but nice to have it all inside Eclipse you know :-)...
Attached debug logs for command and Eclipse run of same pom. Hope you find something in the logs that is helpful.
Regards,
Mauritz
--
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: (MNGECLIPSE-153) deploy gives NPE in wagon-ftp
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-153?page=comments#action_69083 ]
Kenney Westerhof commented on MNGECLIPSE-153:
---------------------------------------------
It seems to be a settings.xml / profile issue.
The eclipse plugin activates the profile default-profile. Is that even defined in your settings.xml?
> deploy gives NPE in wagon-ftp
> -----------------------------
>
> Key: MNGECLIPSE-153
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-153
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Environment: Win 2000 Pro, Sun JDK 1.5.0_06, Maven 2.0.4, Eclipse 3.2 RC2, org.maven.ide.eclipse_0.0.7
> Reporter: Mauritz Lovgren
> Attachments: command.log, eclipse.log
>
>
> When running deploy goal for pom containing ftp deployment, the following NPE is thrown just as files are starting to push to ftp server:
> [INFO] deploy:deploy
> [DEBUG] not adding permissions to wagon connection
> java.lang.NullPointerException
> at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:127)
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:178)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:131)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382)
> at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
> This problem does not occur when running mvn deploy in command prompt.
> I notice a small difference in debug output from Eclipse / command prompt that might be something?
> Eclipse:
> [DEBUG] Found 0 components to load on start
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level settings from: 'C:\dev\ws\ic-sntdispatcher\conf\settings.xml'
> [DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\t539537\.m2\settings.xml'
> [DEBUG] Profile with id: 'default-profile' has been explicitly activated.
> [DEBUG] Profile with id: 'default-profile' has been explicitly activated.
> Command prompt:
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\maven-2.0.2\conf\plugin-registry.xml'
> [INFO] Scanning for projects...
> I have defined ftp server credentials in user home ./m2/settings.xml. Could it be that these credentials are not found when running in Eclipse Maven2 plugin?
> This is not a critical error for me, as I can just deploy using command prompt, but nice to have it all inside Eclipse you know :-)...
> Attached debug logs for command and Eclipse run of same pom. Hope you find something in the logs that is helpful.
> Regards,
> Mauritz
--
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: (MNGECLIPSE-153) deploy gives NPE in wagon-ftp
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-153?page=all ]
Eugene Kuleshov closed MNGECLIPSE-153.
--------------------------------------
Assignee: Eugene Kuleshov
Resolution: Cannot Reproduce
Seems like a wagon issue. Closing, because I can't reproduce it here. Feel free to reopen if you can provide enough information for reproducing, including Eclipse project, poms, settings.xml, etc...
> deploy gives NPE in wagon-ftp
> -----------------------------
>
> Key: MNGECLIPSE-153
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-153
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Environment: Win 2000 Pro, Sun JDK 1.5.0_06, Maven 2.0.4, Eclipse 3.2 RC2, org.maven.ide.eclipse_0.0.7
> Reporter: Mauritz Lovgren
> Assigned To: Eugene Kuleshov
> Attachments: command.log, eclipse.log
>
>
> When running deploy goal for pom containing ftp deployment, the following NPE is thrown just as files are starting to push to ftp server:
> [INFO] deploy:deploy
> [DEBUG] not adding permissions to wagon connection
> java.lang.NullPointerException
> at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:127)
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:178)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:131)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382)
> at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
> This problem does not occur when running mvn deploy in command prompt.
> I notice a small difference in debug output from Eclipse / command prompt that might be something?
> Eclipse:
> [DEBUG] Found 0 components to load on start
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level settings from: 'C:\dev\ws\ic-sntdispatcher\conf\settings.xml'
> [DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\t539537\.m2\settings.xml'
> [DEBUG] Profile with id: 'default-profile' has been explicitly activated.
> [DEBUG] Profile with id: 'default-profile' has been explicitly activated.
> Command prompt:
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\maven-2.0.2\conf\plugin-registry.xml'
> [INFO] Scanning for projects...
> I have defined ftp server credentials in user home ./m2/settings.xml. Could it be that these credentials are not found when running in Eclipse Maven2 plugin?
> This is not a critical error for me, as I can just deploy using command prompt, but nice to have it all inside Eclipse you know :-)...
> Attached debug logs for command and Eclipse run of same pom. Hope you find something in the logs that is helpful.
> Regards,
> Mauritz
--
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: (MNGECLIPSE-153) deploy gives NPE in wagon-ftp
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-153?page=comments#action_69504 ]
Eugene Kuleshov commented on MNGECLIPSE-153:
--------------------------------------------
There are lot of things happens since version 0.0.7... Most likely this issue is already resolved in trunk.
> deploy gives NPE in wagon-ftp
> -----------------------------
>
> Key: MNGECLIPSE-153
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-153
> Project: Maven 2.x Extension for Eclipse
> Type: Bug
> Environment: Win 2000 Pro, Sun JDK 1.5.0_06, Maven 2.0.4, Eclipse 3.2 RC2, org.maven.ide.eclipse_0.0.7
> Reporter: Mauritz Lovgren
> Attachments: command.log, eclipse.log
>
>
> When running deploy goal for pom containing ftp deployment, the following NPE is thrown just as files are starting to push to ftp server:
> [INFO] deploy:deploy
> [DEBUG] not adding permissions to wagon connection
> java.lang.NullPointerException
> at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:127)
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:178)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:131)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382)
> at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
> This problem does not occur when running mvn deploy in command prompt.
> I notice a small difference in debug output from Eclipse / command prompt that might be something?
> Eclipse:
> [DEBUG] Found 0 components to load on start
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level settings from: 'C:\dev\ws\ic-sntdispatcher\conf\settings.xml'
> [DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\t539537\.m2\settings.xml'
> [DEBUG] Profile with id: 'default-profile' has been explicitly activated.
> [DEBUG] Profile with id: 'default-profile' has been explicitly activated.
> Command prompt:
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\maven-2.0.2\conf\plugin-registry.xml'
> [INFO] Scanning for projects...
> I have defined ftp server credentials in user home ./m2/settings.xml. Could it be that these credentials are not found when running in Eclipse Maven2 plugin?
> This is not a critical error for me, as I can just deploy using command prompt, but nice to have it all inside Eclipse you know :-)...
> Attached debug logs for command and Eclipse run of same pom. Hope you find something in the logs that is helpful.
> Regards,
> Mauritz
--
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: (MNGECLIPSE-153) deploy gives NPE in wagon-ftp
Posted by "David Levy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-153?page=comments#action_75435 ]
David Levy commented on MNGECLIPSE-153:
---------------------------------------
It should be a relatively small fix - but a very important one - the Maven plugin for Eclipse almost is rendered useless if it can't do simple things like this.
> deploy gives NPE in wagon-ftp
> -----------------------------
>
> Key: MNGECLIPSE-153
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-153
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Environment: Win 2000 Pro, Sun JDK 1.5.0_06, Maven 2.0.4, Eclipse 3.2 RC2, org.maven.ide.eclipse_0.0.7
> Reporter: Mauritz Lovgren
> Attachments: command.log, eclipse.log
>
>
> When running deploy goal for pom containing ftp deployment, the following NPE is thrown just as files are starting to push to ftp server:
> [INFO] deploy:deploy
> [DEBUG] not adding permissions to wagon connection
> java.lang.NullPointerException
> at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:127)
> at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:178)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:131)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382)
> at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
> This problem does not occur when running mvn deploy in command prompt.
> I notice a small difference in debug output from Eclipse / command prompt that might be something?
> Eclipse:
> [DEBUG] Found 0 components to load on start
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level settings from: 'C:\dev\ws\ic-sntdispatcher\conf\settings.xml'
> [DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\t539537\.m2\settings.xml'
> [DEBUG] Profile with id: 'default-profile' has been explicitly activated.
> [DEBUG] Profile with id: 'default-profile' has been explicitly activated.
> Command prompt:
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\t539537\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\maven-2.0.2\conf\plugin-registry.xml'
> [INFO] Scanning for projects...
> I have defined ftp server credentials in user home ./m2/settings.xml. Could it be that these credentials are not found when running in Eclipse Maven2 plugin?
> This is not a critical error for me, as I can just deploy using command prompt, but nice to have it all inside Eclipse you know :-)...
> Attached debug logs for command and Eclipse run of same pom. Hope you find something in the logs that is helpful.
> Regards,
> Mauritz
--
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