Deployment with wagon-ftp broken
--------------------------------

         Key: MNG-594
         URL: http://jira.codehaus.org/browse/MNG-594
     Project: Maven 2
        Type: Bug
  Components: maven-core  
    Versions: 2.0-alpha-3    
 Environment: Linux proulx.local.net 2.6.8-1.521 #1 Mon Aug 16 09:01:18 EDT 
2004 i686 i686 i386 GNU/Linux
Fresh installation of maven alpha 3. All updates accepted.
 Reporter: Wilfred Springer


Two days ago, it was still possible to deploy artifacts to a remote repository 
using wagon-ftp. (Relevant jar files (wagon-ftp-1.0-alpha-4.jar and 
commons-net-1.1.0.jar) added to $M2_HOME/lib.)

That doesn't work anymore:

m2 deploy
[INFO] 
----------------------------------------------------------------------------
[INFO] Building Maven SableCC Plugin
[INFO] 
----------------------------------------------------------------------------
[INFO] maven-plugin-plugin: resolved to version 2.0-alpha-3 from local 
repository
[INFO] maven-resources-plugin: resolved to version 2.0-alpha-3 from local 
repository
[INFO] maven-compiler-plugin: resolved to version 2.0-alpha-3 from local 
repository
[INFO] maven-surefire-plugin: resolved to version 2.0-alpha-3 from local 
repository
[INFO] maven-jar-plugin: resolved to version 2.0-alpha-3 from local repository
[INFO] maven-install-plugin: resolved to version 2.0-alpha-3 from local 
repository
[INFO] maven-deploy-plugin: resolved to version 2.0-alpha-3 from local 
repository
[INFO] [plugin:descriptor]
[INFO] [resources:resources]
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] Setting reports dir: 
/home/wilfred/workspace/sablecc-plugin/target/surefire-reports
 
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
There are no test to run.
 
Results :
[surefire] Tests run: 0, Failures: 0, Errors: 0
 
[INFO] [jar:jar]
[INFO] Building jar: 
/home/wilfred/workspace/sablecc-plugin/target/sablecc-plugin-1.0-alpha-5-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing 
/home/wilfred/workspace/sablecc-plugin/target/sablecc-plugin-1.0-alpha-5-SNAPSHOT.jar
 to 
/home/wilfred/.m2/repository/sablecc-plugin/sablecc-plugin/1.0-alpha-5-SNAPSHOT/sablecc-plugin-1.0-alpha-5-SNAPSHOT.jar
[INFO] [deploy:deploy]
[INFO] Retrieving snapshot information for sablecc-plugin 1.0-alpha-5-SNAPSHOT
******** Connecting .... ********
******* AHAHAHAHAHAHA ******
****** true *******
---------------------------------------------------
constituent[0]: file:/home/wilfred/local/maven-2.0-alpha-3/lib/oro-2.0.7.jar
constituent[1]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/wagon-http-lightweight-1.0-alpha-4.jar
constituent[2]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/wagon-ftp-1.0-alpha-4.jar
constituent[3]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-project-2.0-alpha-3.jar
constituent[4]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-artifact-2.0-alpha-3.jar
constituent[5]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/doxia-core-1.0-alpha-3.jar
constituent[6]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-plugin-api-2.0-alpha-3.jar
constituent[7]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-reporting-api-2.0-alpha-3.jar
constituent[8]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/wagon-provider-api-1.0-alpha-4.jar
constituent[9]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/commons-validator-1.1.4.jar
constituent[10]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/plexus-input-handler-1.0-alpha-2.jar
constituent[11]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-model-2.0-alpha-3.jar
constituent[12]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-plugin-registry-2.0-alpha-3.jar
constituent[13]: file:/home/wilfred/local/maven-2.0-alpha-3/lib/jsch-0.1.17.jar
constituent[14]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-core-2.0-alpha-3.jar
constituent[15]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-artifact-manager-2.0-alpha-3.jar
constituent[16]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-profile-2.0-alpha-3.jar
constituent[17]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/wagon-file-1.0-alpha-4.jar
constituent[18]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/wagon-ssh-1.0-alpha-4.jar
constituent[19]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-monitor-2.0-alpha-3.jar
constituent[20]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-settings-2.0-alpha-3.jar
constituent[21]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/maven-plugin-descriptor-2.0-alpha-3.jar
constituent[22]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/commons-cli-1.0-beta-2.jar
constituent[23]: file:/home/wilfred/local/maven-2.0-alpha-3/lib/jline-0.9.1.jar
constituent[24]: 
file:/home/wilfred/local/maven-2.0-alpha-3/lib/commons-net-1.1.0.jar
---------------------------------------------------
java.lang.NullPointerException
        at 
org.apache.maven.wagon.providers.ftp.FtpWagon.closeConnection(FtpWagon.java:206)
        at 
org.apache.maven.wagon.AbstractWagon.disconnect(AbstractWagon.java:133)
        at 
org.apache.maven.artifact.manager.DefaultWagonManager.disconnectWagon(DefaultWagonManager.java:480)
        at 
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:403)
        at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:242)
        at 
org.apache.maven.artifact.metadata.AbstractVersionArtifactMetadata.retrieveFromRemoteRepository(AbstractVersionArtifactMetadata.java:94)
        at 
org.apache.maven.artifact.transform.SnapshotTransformation.retrieveFromRemoteRepository(SnapshotTransformation.java:106)
        at 
org.apache.maven.artifact.transform.SnapshotTransformation.transformForDeployment(SnapshotTransformation.java:84)
        at 
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:63)
        at 
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:50)
        at 
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:172)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:401)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:169)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:143)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:129)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103)
        at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:269)
        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:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:363)

The problem is caused (not the root cause though) by the openConnection 
operation on FtpWagon:

    public void openConnection()
        throws ConnectionException, AuthenticationException
    {
        if ( authenticationInfo == null )
        {
            throw new IllegalArgumentException( "Authentication Credentials 
cannot be null for FTP protocol" );
        }

It appears that the authenticationInfo is null, and that the ftp variable 
(FtpClient) is never set, which is causing the NullPointerException when the 
wagon is trying to disconnect. Don't know what caused it. Note that I also 
tried it on the latest HEAD revisions of maven-components en maven-wagon, and I 
got exactly the same problem.


-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to