[
https://issues.apache.org/jira/browse/IVY-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627061#action_12627061
]
Nicolas Lalevée commented on IVY-387:
-------------------------------------
I agree with you, the relative path algorithm should be same every where in the
file. It would be too confusing otherwise.
But I have a preference of having the path relative to ivy settings file. For
me it makes more sense to include other settings of properties relatively to
the ivy settings file itself. Even for a cache definition or a file resolver
definition. If it is relative to the basedir, then the repository and the cache
will then depend path of the project, which is not a good idea for sharing an
ivysettings between several projects.
And then about handling relative paths to an URL, I think we should use
URL.getFile(), so if an ivy settings is served by http, using relative path
would make no sense and things should blows up.
But if a majority agree to use the basedir, I won't put a veto on this, as
having absolute path should always be used here, ivy provides the variables to
fit every use case.
> Absolute and relative path
> --------------------------
>
> Key: IVY-387
> URL: https://issues.apache.org/jira/browse/IVY-387
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 1.4.1
> Reporter: Gilles Scokart
> Assignee: Gilles Scokart
> 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.
