ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (IVY-387) Better and more homogeneous relative paths handling
Date Tue, 02 Sep 2008 12:09:44 GMT

     [ https://issues.apache.org/jira/browse/IVY-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Xavier Hanin resolved IVY-387.
------------------------------

    Resolution: Fixed

I've implemented what Gilles suggested: now relative paths in settings files are allowed for
properties and settings inclusion only. I had to update a lot of unit tests, which were using
relative paths. Now it should work well, and behave more consistently. I've also documented
relative paths handling on the main concept page.

> Better and more homogeneous relative paths handling
> ---------------------------------------------------
>
>                 Key: IVY-387
>                 URL: https://issues.apache.org/jira/browse/IVY-387
>             Project: Ivy
>          Issue Type: Improvement
>    Affects Versions: 1.4.1
>            Reporter: Gilles Scokart
>            Assignee: Xavier Hanin
>             Fix For: 2.0-RC1
>
>
> There are a few of issues in Jira concerning absolute and relative path.  Currently all
the path are resolved relatively to the execution.
> The different issues are :
> - includes in the ivyconf files (IVY-372)
> - properties in the ivyconf files (IVY-89)
> - include configurations in the ivy files (IVY-347) In all case, the path should be resolved
relatively to the including file, and not relatively to the current execution task.
> There is also at least an other issue concerning the path resulutiion in ant task parameter
(IVY-232).
> I think all those problems should be fixed together in order to keep ivy more consistent.
 However, there is a backward compatibility issue: some projects (for which it is required
to launch the build from the base directory) rely on the fact that ivy use path relative to
the current execution directory.  And if they reference files that are not in the base directory,
the change will break their build.
> The first project in that case is ivy itself! Try 'ant -f ivy/build.xml test' and you
will see plenty of test failing.
> Comment from Xavier on the mailing list :
> What could be done is have a single setting somewhere saying if relative paths resolution
should be done in backward compatible mode, or new mode. The default could even be new mode,
if it's clearly documented.

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


Mime
View raw message