ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Updated: (IVY-661) Incorrect parsing artifactPattern attribute in a sftp resolver
Date Thu, 28 Feb 2008 18:21:51 GMT


Xavier Hanin updated IVY-661:

    Fix Version/s: 2.0

> Incorrect parsing artifactPattern attribute in a sftp resolver
> --------------------------------------------------------------
>                 Key: IVY-661
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-beta-2
>         Environment: Developer: Windows XP, jdk1.6.0_02, ant-1.7.0, jsch-0.1.36
> SFTP Server: FreeBSD-6.2-RELEASE.
>            Reporter: Alexey Kiselev
>            Priority: Minor
>             Fix For: 2.0
>         Attachments:
> Ivy settings file contains description of resolver:
> 	<resolvers>
> 		<sftp name="remote">
> 			<ivy pattern="sftp://user:password@host:12345/repository/[module]/[module]-[revision].xml"/>
> 			<artifact pattern="sftp://user:password@host:12345/repository/[module]/[artifact]-[revision].[ext]"/>
> 		</sftp>
> 	</resolvers>
> Then we try to publish to a repository for the first time on empty server we get a
and a following directory structure created on the server ~user/sftp:/.
> Afterwards when we publish for the second time we get following directory structure ~user/sftp:/user:password@host:12435/repository/module/
and successfully published artifact.
> During the first run the caused by creation of a directory with empty
name. Creation of the directory with empty name caused by double slash (//) following "sftp:".
> Then if we try to retrieve a file from the repository we get an exception with message
"reolving resource error: No such file". This problem appears because after establishing connection
to the sftp server we are automatically moved to the user home directory. 
> Thats why we must use a relative path in put, get and list commands when we work with
a repository.
> Solution of this problem is in the attached patch.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message