You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Peter Donald <do...@apache.org> on 2001/11/10 08:19:40 UTC
[phoenix] xerces.jar
Hi,
If you don't build phoenix via the build scripts you are going to have to add
a property into you ant.properties file that specifies the location of the
xerces jar for it to build from now on. See ant.properties.sample for an
example of it.
--
Cheers,
Pete
*------------------------------------------------------*
| "Nearly all men can stand adversity, but if you want |
| to test a man's character, give him power." |
| -Abraham Lincoln |
*------------------------------------------------------*
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [phoenix] xerces.jar
Posted by Peter Donald <do...@apache.org>.
oh - got it now. My mail server seems to be wonky again ;)
On Sun, 11 Nov 2001 06:00, Stephen McConnell wrote:
> Pete:
>
> Being someone who (a) does not use the build scipts, and (b) does not need
> xerces.jar because development here is on JDK 1.4, the solution proposed
> below doesn't work. The termorary workaround I have added to my version of
> the phoenix build is the following
>
> // from check-environment
>
> <available property="xerces.present" type="file" file="${xerces.jar}"/>
>
> // from "dist-lite"
>
> <copy todir="${bin.dist.lib}">
> <fileset dir="${lib.dir}">
> <include name="xerces.jar" if="xerces.present"/>
> </fileset>
> </copy>
>
> The problem here is that this does not use the "{xerces.jar}" property
> because the ${xerces.jar} defines a path and I can only apply the "if" test
> on a filename include. The clean solution would be to seperate the xerces
> directory path from the filename - ${xerces.dir}/${xerces.file}. That
> would allow something like the following:
>
> // from check-environment
>
> <available property="xerces.present" type="file"
> file="${xerces.dir}/${xerces.file}"/>
>
> // from "dist-lite"
>
> <copy todir="${bin.dist.lib}">
> <fileset dir="${xerces.dir}">
> <include name="${xerces.file}" if="xerces.available"/>
> </fileset>
> </copy>
>
> So instead of documenting ${xerces.jar} in the ant.properties.sample file,
> you could instead document ${xerces.dir} and ${xerces.jar} and maintain the
> defintion of ${xerces.jar} in the build file.
>
> Steve.
>
> > -----Original Message-----
> > From: Peter Donald [mailto:donaldp@apache.org]
> > Sent: Saturday, 10 November, 2001 08:20
> > To: Avalon Development
> > Subject: [phoenix] xerces.jar
> >
> >
> > Hi,
> >
> > If you don't build phoenix via the build scripts you are going to
> > have to add
> > a property into you ant.properties file that specifies the
> > location of the
> > xerces jar for it to build from now on. See ant.properties.sample for an
> > example of it.
> >
> > --
> > Cheers,
> >
> > Pete
> >
> > *------------------------------------------------------*
> >
> > | "Nearly all men can stand adversity, but if you want |
> > | to test a man's character, give him power." |
> > | -Abraham Lincoln |
> >
> > *------------------------------------------------------*
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
--
Cheers,
Pete
---------------------------------
I think not; therefore I ain't...
---------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [phoenix] xerces.jar
Posted by Stephen McConnell <mc...@osm.net>.
Pete:
Being someone who (a) does not use the build scipts, and (b) does not need
xerces.jar because development here is on JDK 1.4, the solution proposed
below doesn't work. The termorary workaround I have added to my version of
the phoenix build is the following
// from check-environment
<available property="xerces.present" type="file" file="${xerces.jar}"/>
// from "dist-lite"
<copy todir="${bin.dist.lib}">
<fileset dir="${lib.dir}">
<include name="xerces.jar" if="xerces.present"/>
</fileset>
</copy>
The problem here is that this does not use the "{xerces.jar}" property
because the ${xerces.jar} defines a path and I can only apply the "if" test
on a filename include. The clean solution would be to seperate the xerces
directory path from the filename - ${xerces.dir}/${xerces.file}. That would
allow something like the following:
// from check-environment
<available property="xerces.present" type="file"
file="${xerces.dir}/${xerces.file}"/>
// from "dist-lite"
<copy todir="${bin.dist.lib}">
<fileset dir="${xerces.dir}">
<include name="${xerces.file}" if="xerces.available"/>
</fileset>
</copy>
So instead of documenting ${xerces.jar} in the ant.properties.sample file,
you could instead document ${xerces.dir} and ${xerces.jar} and maintain the
defintion of ${xerces.jar} in the build file.
Steve.
> -----Original Message-----
> From: Peter Donald [mailto:donaldp@apache.org]
> Sent: Saturday, 10 November, 2001 08:20
> To: Avalon Development
> Subject: [phoenix] xerces.jar
>
>
> Hi,
>
> If you don't build phoenix via the build scripts you are going to
> have to add
> a property into you ant.properties file that specifies the
> location of the
> xerces jar for it to build from now on. See ant.properties.sample for an
> example of it.
>
> --
> Cheers,
>
> Pete
>
> *------------------------------------------------------*
> | "Nearly all men can stand adversity, but if you want |
> | to test a man's character, give him power." |
> | -Abraham Lincoln |
> *------------------------------------------------------*
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>