Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: wagon-ssh
-
Labels:None
-
Environment:HideC:\MavenTest\dhe>mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-07 00:46:01+0530)
Java version: 1.5.0
Java home: C:\Program Files\IBM\Java50\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Famil
y: "dos"ShowC:\MavenTest\dhe>mvn -version Apache Maven 2.2.1 (r801777; 2009-08-07 00:46:01+0530) Java version: 1.5.0 Java home: C:\Program Files\IBM\Java50\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Famil y: "dos"
-
Number of attachments :
Description
I am unable to deploy vesion with SNAPSHOT in my remote location using sftp.
here error is attached in .txt format.
We encountered a very similar error lately after a patch was installed on our solaris server.
I tracked down the problem to the class org.apache.maven.wagon.providers.ssh.jsch.ScpWagon: when trying to lookup the file .../maven-metadata.xml for any new snapshot version the method fillInputData detects the error code 1 and then validates the error message to contain the text No such file or directory. Only then a ResourceDoesNotExistException will be thrown, indicating that the requested file does not exist.
Unfortunately, the error messages are returned in german since the solaris patch has been installed (Datei oder Verzeichnis existiert nicht). Therefore an IOException will be thrown instead of the ResourceDoesNotExistException. This will stop the deployment of the new snapshot version immediately.
We are still working on a solution. In the meantime we have to create target directories, maven-metadata.xml files, and maven-metadata.xml.sha1 files manually as workaround. Very, very anoying.