Here is a real example of what Dominique is referring to.
<project name="L10NProcess" basedir="." default="init">
<description>
L10N project for a product. This is intended to be imported into a
project for a product or part of a product. The targets in this file will be
accessible via the product project. The product project will contain the
properties that are specific to that project. This project relies on the
product properties being set before any of the targets can be used.
</description>
<!-- Load the macros and support tasks files. -->
<import file="${env.LEVTOOLSDIR}/L10NProcess/L10NProcess-macros.xml"/>
<import file="${env.LEVTOOLSDIR}/L10NProcess/L10NProcess-tasks.xml"/>
.
.
.
<target name="init" description="Initialization: Set up properties
needed throughout this project.">
.
.
.
<property file="${USER}.properties"/>
.
.
.
In this example, if all the .xml files are contained in db blobs what would
I need to do to the <import> to make this work? How could I develop the XML
file using the file system them store it in the db without changing it?
If the .xml file is contained in a db blob where is the ${USER}.properties
stored? If in the db, what assumption can be made about the key to identify
it? If on the file system, what assumption can be made about its directory
name.
Thanks. Bill
Bill Rich
Wilandra Consulting LLC
1325 Addiewell Place
San Jose, CA 95120-3905
phone: +1 408 268-2452
mobile: +1 408 410-9713
Santa Cruz: +1 831 464-9007
fax: +1 413 669-9716
[EMAIL PROTECTED]
http://www.wilandra.com
-----Original Message-----
From: Erskine, Chris [mailto:[EMAIL PROTECTED]
Sent: Friday, October 15, 2004 7:52 AM
To: Ant Users List
Subject: RE: AW: parsing ant build scripts from unusual sources
So, if I understand you right, you are saying that because the build.xml
file was not read from the file system, I will have problems assuming where
the other files like .properties files will be? I guess that I would have
the same types of issues on things like where the source files are located
and where I want to build to.
This is an issue that I have even if I read the file from the file system.
I have to have a reference point for where any file is located. Most times,
this is based upon the basedir. By default, basedir is set based upon where
the build.xml file is located but ant has ways to change this value and a
different assumption can be used when the build file comes from a new source
like a database. From the comment Robert made, I expect that this would be
fixed by changing the documentation to state that the default is PWD when
the build file does not come from the file system.
I think that Robert can start boasting (although I think that it was really
a comment to see if people had real issues).
Chris Erskine
EDS Consulting Services
F5-EDS-001
2424 Garden of the Gods Rd
Colorado Springs, CO 80919
Phone: 719-535-6064
Phone:
mailto:[EMAIL PROTECTED]
-----Original Message-----
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Friday, October 15, 2004 8:10 AM
To: Ant Users List
Subject: RE: AW: parsing ant build scripts from unusual sources
> -----Original Message-----
> From: Robert Dockins [mailto:[EMAIL PROTECTED] It seems to me
> that the restriction is mostly in people's heads :)
Hmmm... The fact is that no build uses anything else than File-based build
files at this point. Just try to use a resource from an imported build
'stream', like for example a .properties file, without making assumptions
where the imported build is coming from (i.e. load the resource relative to
the imported build, wherever it is).
Until you've got that working, don't boast too quickly ;-) --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
