[
https://issues.apache.org/jira/browse/IVY-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620544#action_12620544
]
Xavier Hanin commented on IVY-232:
----------------------------------
Fixing this is not complex, it's only time consuming to go through all the code
to make sure we don't forget any single case. And when I talk about absolute
paths, I'm actually talking about paths relative to a directory which has an
absolute path, like path relative to basedir or settings dir. For a first
reference to this "trick", see [this
comment|https://issues.apache.org/jira/browse/IVY-232?focusedCommentId=12453138#action_12453138]
> 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: Gilles Scokart
> Fix For: 2.0-RC1
>
>
> 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.
