[
https://issues.apache.org/jira/browse/IVY-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVY-232.
------------------------------
Resolution: Fixed
I've resolved this issue, now all relative files should be relative to the base
directory set in IvySettings, which defaults to current directory, except when
used from Ant, in which case it's the Ant basedir which is used.
I say all, but it's not true. Indeed, some work has already been done in the
settings parsing to handle properties file and settings inclusion path
specifically. I will discuss that on IVY-387, since this is not only related to
this issue but is more general about absolute and relative paths.
> Incorrect directory path resolve when running from a different directory
> ------------------------------------------------------------------------
>
> Key: IVY-232
> URL: https://issues.apache.org/jira/browse/IVY-232
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 1.3-RC2
> Environment: Windows 2000 (probably Unix also. Didn't check that)
> Reporter: easyproglife
> Assignee: Xavier Hanin
> Fix For: 2.0-RC1
>
> Attachments: ivy-232-patch.txt
>
>
> Suppose you have two projects in two directories:
> /projA
> /projB
> Each one of them have its own build.xml.
> When you run Ant on /projA/build.xml from /projA evrything is ok.
> When you run from "/projB" "ant -f ..\projA\build.xml" relative pathes are
> based on "projB" by Ivy, whereas the correct way (as Ant and Maven works) is
> to use "projA" as the base directory (assuming "/projA/build.xml" has
> "basedir" attribute: ".")
> In other words, Ivy should take the base directory as specified in the
> "build.xml" file in "project" tag in "basedir" attribute, and calculate it
> based on the location of the build.xml file; not based on the "current"
> directory where Ant was invoced from.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
