maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Moved: (WAGON-201) SftpWagon should throw ResourceDoesNotExistException when possible
Date Wed, 14 May 2008 07:37:30 GMT

     [ http://jira.codehaus.org/browse/WAGON-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter moved WAGONSSH-16 to WAGON-201:
--------------------------------------------

    Fix Version/s:     (was: 1.0-alpha-5)
                   1.0-alpha-5
      Component/s:     (was: wagon-ssh)
                   wagon-ssh
              Key: WAGON-201  (was: WAGONSSH-16)
          Project: Maven Wagon  (was: wagon-ssh)

> SftpWagon should throw ResourceDoesNotExistException when possible
> ------------------------------------------------------------------
>
>                 Key: WAGON-201
>                 URL: http://jira.codehaus.org/browse/WAGON-201
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-ssh
>            Reporter: Juan F. Codagnone
>            Assignee: Brett Porter
>             Fix For: 1.0-alpha-5
>
>         Attachments: WAGONSSH-16.diff
>
>
> (this is one is like MNG-925 buf for ssh)
> maven-artifact-manager (via DefaultRepositoryMetadataManager#resolveAlways) relays on
ResourceDoesNotExistException to manage metadata. This cause an error during the deploy of
artifacts (see the backtrace)
> The excepcion could be analized (it  depends on the version jsch, but at least let you
deploy). A background question is what will happen with DefaultRepositoryMetadataManager and
the wagons that doesn't support detectecting that the file was not found.
> [INFO] Diagnosis: Error deploying artifact
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error deploying artifact
>         at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:154)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:362)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
>         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: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)
> Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying
artifact:
>         at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:89)
>         at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:53)
>         at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:142)
>         ... 16 more
> Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable
to retrieve metadata
>         at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositoryMetadataManager.java:212)
>         at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:230)
>         at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
>         ... 18 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Error occured while downloading
`ar/com/test/maven/poms/bare/maven-metadata.xml'from the remote repository:[test-private-repo]
-> sftp://localhost/tmp/m2
>         at org.apache.maven.wagon.providers.ssh.ScpWagon.handleGetException(ScpWagon.java:600)
>         at org.apache.maven.wagon.providers.ssh.SftpWagon.getIfNewer(SftpWagon.java:283)
>         at org.apache.maven.wagon.providers.ssh.SftpWagon.get(SftpWagon.java:297)
>         at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:339)
>         at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:269)
>         at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositoryMetadataManager.java:198)
>         ... 20 more
> Caused by: No such file
>         at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:1541)
>         at com.jcraft.jsch.ChannelSftp.stat(ChannelSftp.java:1207)
>         at com.jcraft.jsch.ChannelSftp.get(ChannelSftp.java:587)
>         at com.jcraft.jsch.ChannelSftp.get(ChannelSftp.java:559)
>         at org.apache.maven.wagon.providers.ssh.SftpWagon.getIfNewer(SftpWagon.java:263)
>         ... 24 more

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

        

Mime
View raw message