You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Anthony W. Marino" <an...@AWMObjects.com> on 2002/05/27 20:36:12 UTC
"j-t-c/jk/native(2) build.xml": Global Server Property Initialization Issue
For example, the "apache13.home" property is set with too a generic/common
directory location which should, 100% of the time, evaluate to true when
checked with an "available" task (ie; target "detect").
This global assignment will only occur, of course, when one has purposely
commented-out (indicating apache13 not available) or inadvertantly omitted
that particular property from a properties file.
Several possible solutions:
1) Initialize the property with a more specific dir path (ie;
/usr/local/apache13 (see "apache2.home" intialization). Only issue here is
if the user had several installs of apache13 including in the default path
and intended to use another installation path.
2) Remove the global assignment and make it a prerequisite for the user to add
this to a properties file which will always fail if not preset in a
properties file.
If you are going to setup global properties in "build.xml" maybe some
conditional statements are in order, where applicable, to be more os
specific/compliant. Or mabe os specific properties files that could be
generated/used automatically?
Thanks,
Anthony
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: "j-t-c/jk/native(2) build.xml": Global Server Property Initialization Issue
Posted by "Anthony W. Marino" <an...@AWMObjects.com>.
On Monday 27 May 2002 02:36 pm, Anthony W. Marino wrote:
> For example, the "apache13.home" property is set with too a generic/common
> directory location which should, 100% of the time, evaluate to true when
> checked with an "available" task (ie; target "detect").
Note that "True" is when running on *nix implementations.
Anthony
> This global assignment will only occur, of course, when one has purposely
> commented-out (indicating apache13 not available) or inadvertantly omitted
> that particular property from a properties file.
>
>
> Several possible solutions:
>
> 1) Initialize the property with a more specific dir path (ie;
> /usr/local/apache13 (see "apache2.home" intialization). Only issue here is
> if the user had several installs of apache13 including in the default path
> and intended to use another installation path.
>
> 2) Remove the global assignment and make it a prerequisite for the user to
> add this to a properties file which will always fail if not preset in a
> properties file.
>
>
> If you are going to setup global properties in "build.xml" maybe some
> conditional statements are in order, where applicable, to be more os
> specific/compliant. Or mabe os specific properties files that could be
> generated/used automatically?
>
> Thanks,
> Anthony
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: "j-t-c/jk/native(2) build.xml": Global Server Property Initialization Issue
Posted by "Anthony W. Marino" <an...@AWMObjects.com>.
Jean-Frederic,
If it isn't too much trouble, just initialize "apache13.home" property in
"j-t-c/jk/native(2) build.xml" to "/opt/apache13". This will be consistant
with how "apache2.home" is initialized and goes toward a more specific
initialization.
Thank You,
Anthony
> Anthony W. Marino wrote:
> > For example, the "apache13.home" property is set with too a
> > generic/common directory location which should, 100% of the time,
> > evaluate to true when checked with an "available" task (ie; target
> > "detect").
> >
> > This global assignment will only occur, of course, when one has
> > purposely commented-out (indicating apache13 not available) or
> > inadvertantly omitted that particular property from a properties file.
> >
> >
> > Several possible solutions:
> >
> > 1) Initialize the property with a more specific dir path (ie;
> > /usr/local/apache13 (see "apache2.home" intialization). Only issue here
> > is if the user had several installs of apache13 including in the default
> > path and intended to use another installation path.
> >
> > 2) Remove the global assignment and make it a prerequisite for the user
> > to add this to a properties file which will always fail if not preset in
> > a properties file.
> >
> >
> > If you are going to setup global properties in "build.xml" maybe some
> > conditional statements are in order, where applicable, to be more os
> > specific/compliant. Or mabe os specific properties files that could be
> > generated/used automatically?
>
> The configure of native2 build the ../build.properties out of the
> ../build.properties.autoconf
>
> > Thanks,
> > Anthony
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org> For additional
> > commands, e-mail: <ma...@jakarta.apache.org>
--
Anthony W. Marino
Pres./CTO, AWM Objects
email: anthony@AWMObjects.com
phone: (732) 610-2441
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: "j-t-c/jk/native(2) build.xml": Global Server Property Initialization Issue
Posted by "Anthony W. Marino" <an...@AWMObjects.com>.
> Anthony W. Marino wrote:
> > For example, the "apache13.home" property is set with too a
> > generic/common directory location which should, 100% of the time,
> > evaluate to true when checked with an "available" task (ie; target
> > "detect").
> >
> > This global assignment will only occur, of course, when one has
> > purposely commented-out (indicating apache13 not available) or
> > inadvertantly omitted that particular property from a properties file.
> >
> >
> > Several possible solutions:
> >
> > 1) Initialize the property with a more specific dir path (ie;
> > /usr/local/apache13 (see "apache2.home" intialization). Only issue here
> > is if the user had several installs of apache13 including in the default
> > path and intended to use another installation path.
> >
> > 2) Remove the global assignment and make it a prerequisite for the user
> > to add this to a properties file which will always fail if not preset in
> > a properties file.
> >
> >
> > If you are going to setup global properties in "build.xml" maybe some
> > conditional statements are in order, where applicable, to be more os
> > specific/compliant. Or mabe os specific properties files that could be
> > generated/used automatically?
>
> The configure of native2 build the ../build.properties out of the
> ../build.properties.autoconf
>
Isn't that for configure/make process and not for ant? Also, that still
doesn't take care of "native" build process with ant.
Anthony
> > Thanks,
> > Anthony
> >
> >
> >
> >
> > --
> > 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>
Re: "j-t-c/jk/native(2) build.xml": Global Server Property Initialization
Issue
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Anthony W. Marino wrote:
> For example, the "apache13.home" property is set with too a generic/common
> directory location which should, 100% of the time, evaluate to true when
> checked with an "available" task (ie; target "detect").
>
> This global assignment will only occur, of course, when one has purposely
> commented-out (indicating apache13 not available) or inadvertantly omitted
> that particular property from a properties file.
>
>
> Several possible solutions:
>
> 1) Initialize the property with a more specific dir path (ie;
> /usr/local/apache13 (see "apache2.home" intialization). Only issue here is
> if the user had several installs of apache13 including in the default path
> and intended to use another installation path.
>
> 2) Remove the global assignment and make it a prerequisite for the user to add
> this to a properties file which will always fail if not preset in a
> properties file.
>
>
> If you are going to setup global properties in "build.xml" maybe some
> conditional statements are in order, where applicable, to be more os
> specific/compliant. Or mabe os specific properties files that could be
> generated/used automatically?
The configure of native2 build the ../build.properties out of the
../build.properties.autoconf
>
> Thanks,
> Anthony
>
>
>
>
> --
> 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>