Login | Register
My pages Projects Community openCollabNet

Discussions > users > interpretation of relative paths in build.xml

antelope
Discussion topic

Hide all messages in topic

All messages in topic

RE: interpretation of relative paths in build.xml

Author danson at germane-software dot com
Full name danson at germane-software dot com
Date 2004-05-26 14:32:59 PDT
Message Matt,

Glad to hear it worked out for you. In the mean time, I've fixed the
relative path problem. The fix will be in the 3.1.8 release of Antelope.

Dale


> Thanks Dale
>
> I tried Ant 1.6 and <import> and it solved the problem - I can now include
> a
> common targets file specifying a relative path
>
> Matt
>
> -----Original Message-----
> From: Dale Anson [mailto:danson@germa​ne-software.com]
> Sent: 24 May 2004 16:00
> To: users at antelope dot tigris dot org
> Subject: Re: interpretation of relative paths in build.xml
>
>
> Hi Matt,
>
> It sounds like a bug to me. Relative paths should work. I'll take a
> look. Also, if you can use Ant 1.6.x, you can use the new <import> task,
> which is actually a nicer way of including common targets.
>
> Dale
>
>
> Matt Harrison wrote:
>
>> Hi
>>
>> Using: Antelope 3.1.7, Ant 1.5.4, SDK 1.4.2_04, Windows 2000 Prof, jEdit
>> 4.2pre13
>>
>> I'm having a problem with a relative path setting in a build.xml file
>> that
>> worked previously with ant farm on jEdit
>>
>> I get an error beginning: "Error loading included resource file" when
>> loading a build.xml file that includes:
>>
>> <!DOCTYPE project [
>> <!ENTITY targets SYSTEM "../targets.xml">
>> ]>
>>
>> &targets;
>>
>> whereby the error message indicates that it is searching for
>> ../tagets.xml
>> relative to the home directory of jEdit (and relative to the home
> directory
>> of Antelope in stand alone mode) rather than relative to the build file
>> itself (where targets.xml is located)
>>
>> Is there any way of resolving this other than using absolute paths in my
>> build.xml files?
>>
>> Thanks, Matt
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
>> For additional commands, e-mail: users-help at antelope dot tigris dot org
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
> For additional commands, e-mail: users-help at antelope dot tigris dot org
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
> For additional commands, e-mail: users-help at antelope dot tigris dot org
>
>



--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
For additional commands, e-mail: users-help at antelope dot tigris dot org

RE: interpretation of relative paths in build.xml

Author mattha
Full name Matthew Harrison
Date 2004-05-26 03:04:19 PDT
Message Thanks Dale

I tried Ant 1.6 and <import> and it solved the problem - I can now include a
common targets file specifying a relative path

Matt

-----Original Message-----
From: Dale Anson [mailto:danson@germa​ne-software.com]
Sent: 24 May 2004 16:00
To: users at antelope dot tigris dot org
Subject: Re: interpretation of relative paths in build.xml


Hi Matt,

It sounds like a bug to me. Relative paths should work. I'll take a
look. Also, if you can use Ant 1.6.x, you can use the new <import> task,
which is actually a nicer way of including common targets.

Dale


Matt Harrison wrote:

> Hi
>
> Using: Antelope 3.1.7, Ant 1.5.4, SDK 1.4.2_04, Windows 2000 Prof, jEdit
> 4.2pre13
>
> I'm having a problem with a relative path setting in a build.xml file that
> worked previously with ant farm on jEdit
>
> I get an error beginning: "Error loading included resource file" when
> loading a build.xml file that includes:
>
> <!DOCTYPE project [
> <!ENTITY targets SYSTEM "../targets.xml">
> ]>
>
> &targets;
>
> whereby the error message indicates that it is searching for ../tagets.xml
> relative to the home directory of jEdit (and relative to the home
directory
> of Antelope in stand alone mode) rather than relative to the build file
> itself (where targets.xml is located)
>
> Is there any way of resolving this other than using absolute paths in my
> build.xml files?
>
> Thanks, Matt
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
> For additional commands, e-mail: users-help at antelope dot tigris dot org
>

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
For additional commands, e-mail: users-help at antelope dot tigris dot org

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
For additional commands, e-mail: users-help at antelope dot tigris dot org

Re: interpretation of relative paths in build.xml

Author Dale Anson <danson at germane-software dot com>
Full name Dale Anson <danson at germane-software dot com>
Date 2004-05-24 08:00:06 PDT
Message Hi Matt,

It sounds like a bug to me. Relative paths should work. I'll take a
look. Also, if you can use Ant 1.6.x, you can use the new <import> task,
which is actually a nicer way of including common targets.

Dale


Matt Harrison wrote:

> Hi
>
> Using: Antelope 3.1.7, Ant 1.5.4, SDK 1.4.2_04, Windows 2000 Prof, jEdit
> 4.2pre13
>
> I'm having a problem with a relative path setting in a build.xml file that
> worked previously with ant farm on jEdit
>
> I get an error beginning: "Error loading included resource file" when
> loading a build.xml file that includes:
>
> <!DOCTYPE project [
> <!ENTITY targets SYSTEM "../targets.xml">
> ]>
>
> &targets;
>
> whereby the error message indicates that it is searching for ../tagets.xml
> relative to the home directory of jEdit (and relative to the home directory
> of Antelope in stand alone mode) rather than relative to the build file
> itself (where targets.xml is located)
>
> Is there any way of resolving this other than using absolute paths in my
> build.xml files?
>
> Thanks, Matt
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
> For additional commands, e-mail: users-help at antelope dot tigris dot org
>

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
For additional commands, e-mail: users-help at antelope dot tigris dot org

interpretation of relative paths in build.xml

Author mattha
Full name Matthew Harrison
Date 2004-05-24 07:10:36 PDT
Message Hi

Using: Antelope 3.1.7, Ant 1.5.4, SDK 1.4.2_04, Windows 2000 Prof, jEdit
4.2pre13

I'm having a problem with a relative path setting in a build.xml file that
worked previously with ant farm on jEdit

I get an error beginning: "Error loading included resource file" when
loading a build.xml file that includes:

<!DOCTYPE project [
  <!ENTITY targets SYSTEM "../targets.xml">
]>

  &targets;

whereby the error message indicates that it is searching for ../tagets.xml
relative to the home directory of jEdit (and relative to the home directory
of Antelope in stand alone mode) rather than relative to the build file
itself (where targets.xml is located)

Is there any way of resolving this other than using absolute paths in my
build.xml files?

Thanks, Matt

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@an​telope.tigris.org
For additional commands, e-mail: users-help at antelope dot tigris dot org
Messages per page: