[
https://issues.apache.org/jira/browse/IVY-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620543#action_12620543
]
Adrian Sandor commented on IVY-232:
-----------------------------------
I'd provide a patch, but first I'd need to figure out how to fix it (and that
would take some time). I thought you guys could do it very easily, and just
haven't decided to do it yet.
Absolute paths are unacceptable because the projects may be installed (from
svn) in different locations on different computers; only the relative paths
would be the same.
The "${basedir}/" thing seems to be an acceptable workaround (thank you!),
hadn't thought about that or seen it mentioned before. Still, I think this bug
should be fixed.
> 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.
