[ http://jira.codehaus.org/browse/MNGECLIPSE-153?page=all ]
Kenney Westerhof moved MECLIPSE-105 to MNGECLIPSE-153:
------------------------------------------------------
Key: MNGECLIPSE-153 (was: MECLIPSE-105)
Project: Maven 2.x Extension for Eclipse (was: Maven 2.x Eclipse Plugin)
> 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
