Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of xavier.hanin@gmail.com
 designates 209.85.217.18 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=j2LrNpdLRzn5GE4b/YJJlrPSq5UBUG/nbZQ3gw8Sg22b57PcW162WUmIZHdcTUxFM+
         sX8CPplYmM5YLEHGxPD/K+4ymjJZN5KCtt9DVb1H+cG6mkvKXEIt5JtaCzsf4vkalvWN
         fE8Tvcp+ek5V/+/1aw01GxeyJVR3zML9A+oJY=
Message-ID: <635a05060809170020l37dc1ad6h139912a5cf8d0896@mail.gmail.com>
Date: Wed, 17 Sep 2008 09:20:39 +0200
From: "Xavier Hanin" <xavier.hanin@gmail.com>
To: ivy-user@ant.apache.org
Subject: Re: Experience with ivy from SVN (2008-09-16)
In-Reply-To: 
 <B6CF1054FDC8B845BF93A6645D19BEA35536B9AB99@GVW1118EXC.americas.hpqcorp.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_9155_25299967.1221636039847"
References: 
 <B6CF1054FDC8B845BF93A6645D19BEA35536B9AB99@GVW1118EXC.americas.hpqcorp.net>

------=_Part_9155_25299967.1221636039847
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Tue, Sep 16, 2008 at 6:43 PM, Seaborne, Andy <andy.seaborne@hp.com>wrote:

> Hi there,
>
> I just tried building ivy from SVN then using it on a project.  I had two
> minor problems which don't seem to be in the CHANGES file (but I'm a
> beginner with Ivy so they may be expressed in language I didn't grok) and
> one case of something seeming wrong in 2.0.0-beta and SVN.
>
> Are these intentional changes or am I unlucky?

The way Ivy deals with paths has changed in rc1, this is intentional. Paths
handling is documented on the "Main Concepts" page available on trunk or in
the rc1 attempt uploaded yesterday.

In rc1, most paths in settings files must be absolute. It seems that the
File#isAbsolute() method does not return true for a unix like path under
cygwin, this is the root of your problem. I'm not sure if this is something
that we can address or not, please file a bug in JIRA. Another problem I see
is that the error reporting is not nice, if the problem is "only" a problem
of absolute path, it should be mentionned, because the current error message
is very cryptic for a user. This can be reported in a separate JIRA.

That being said, as there is a workaround and only occurs in some
environment (cygwin), I don't think this is a blocking issue for
2.0.0.Since we have just started our 2.0.0 release candidates cycles,
I think this
will rather be fixed in a 2.0.x version, unless other blocking bugs are
raised and this one is fixed along with the blocking ones in a next RC.

For your problem #2, this is indeed a change in rc, the solution is to
prefix your pattern with ${ivy.settings.dir} or with ${user.home}.

For #3, this may be a blocking issue, but I'm really surprised this has not
been reported before. Could you setup a small test case reproducing this
problem?

Xavier


>
>
> Ant 1.7.1
> Ivy 20080916162121
> Java: 1.6.0_07
> Vista (up to date)
> Cygwin (up to date as of last week)
>
>
> 1/ sftp resolver
>
> UNIX style file name for key file no longer accepted.
>
> Running on Cygwin on Windows Vista
>
> With the SVN build:
> ...
> [ivy:resolve] :: Ivy 2.0.0-rc1-local-20080916162121 - 20080916162121 ::
> http://ant.apache.org/ivy/ ::
> :: loading settings :: file = c:\home\afs\Projects\TDB\ivysettings.xml
>
> BUILD FAILED
> c:\home\afs\Projects\TDB\build-lib.xml:357: impossible to configure
> ivy:settings with given file: c:\home\afs\Projects\TDB\ivysettings.xml :
> java.text.ParseException: failed to load settings from
> file:/c:/home/afs/Projects/TDB/ivysettings.xml: impossible to convert
> /home/afs/.ssh/ivy-pub-jena-key to class java.io.File for setting keyFile on
> class org.apache.ivy.plugins.resolver.SFTPResolver
>
> This works with 2.0.0-beta
>
> From ivysetting.xml:
>
>    <sftp name="dev-publish" host="jena.hpl.hp.com"
>          user="${env.IVYUSER}" keyFile="${env.IVYKEY}">
>      <ivy pattern="repo-dev/com/hp/hpl/jena/[module]/[revision]/ivy.xml"/>
>      <artifact
> pattern="repo-dev/com/hp/hpl/jena/[module]/[revision]/[artifact]-[revision].[ext]"/>
>    </sftp>
>
> And env.IVYUSER is "afs" and env.IVYKEY is
> "/home/afs/.ssh/ivy-pub-jena-key"
>
> If I set IVYKEY to a windows style path, c:\home\afs\.ssh\ivy-pub-jena-key
> it works with the SVN version and in 2.0.0-beta.
>
>
> 2/ Filesystem resolver
> ...
> c:\home\afs\Projects\TDB\build-lib.xml:357: impossible to configure
> ivy:settings with given file: c:\home\afs\Projects\TDB\ivysettings.xml :
> java.text.ParseException: failed to load settings from
> file:/c:/home/afs/Projects/TDB/ivysettings.xml: impossible to add configured
> child for ivy on class org.apache.ivy.plugins.resolver.FileSystemResolver:
> ivy pattern must be absolute: build/pub/[module]-[revision]/ivy.xml
>
> ivysettings.xml:
>
>    <filesystem name="dev-resolver" >
>       <ivy      pattern="build/pub/[module]-[revision]/ivy.xml"/>
>       <artifact
> pattern="build/pub/[module]-[revision]/[artifact]-[revision].[ext]"/>
>    </filesystem>
>
> I use this to quickly test the publishing process so it isn't particularly
> important to me but it would be nice.
>
> Using \ for / does not make a difference.
> Using "/home/afs/Projects/TDB/build/pub..." does not work.
> Using "c:\home\afs\Projects\TDB\build\pub\..." does work.
>
> In my cygwin installation /home/afs as c:\home\afs so there is a pun going
> on but I was hoping to use the same setup across windows and Linux and be
> neutral to file separator (and ideally file system location).
>
> org.apache.ivy.util.Checks.java is doing  "f.isAbsolute()" which makes it
> sensitive to the filename format.
>
>
> In both cases, build-lib.xml:357 is the task:
>  <target name="ivy-resolve-report" depends="ivy-init">
>    <ivy:resolve conf="dev"
>                 haltonfailure="false"
> failureproperty="ivy.resolve.failed"/>
>    <ivy:report todir="${reports.dir}"/>
>    <fail message="Ivy dependency failed" if="ivy.resolve.failed"/>
>  </target>
>
> The complete files can be picked up from
> https://jena.svn.sourceforge.net/svnroot/jena/TDB/trunk/ revision 4630
>
>
> 3/ With ivy-2.0.0-beta and ivy SVN:
>
> The filesystem resolver seems to publish the wrong bytes (i.e. different
> from the sftp resolver).
>
> My build artifacts are:
> 2011 bytes --    ivy-0.5.4-dev.jar
> 478122 bytes --  tdb-0.5.4-dev.jar
> 2239 --          tdb-0.5.4-dev.pom
>
> But the published tdb-0.5.4-dev.pom is the bytes for tdb-0.5.4-dev.jar
> (478122 is them)
>
>        Andy
>
> --------------------------------------------
>  Hewlett-Packard Limited
>  Registered Office: Cain Road, Bracknell, Berks RG12 1HN
>  Registered No: 690597 England
>
>


-- 
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/

------=_Part_9155_25299967.1221636039847--