Hi,

maybe this works on Unix, but not on M$ or did I do it wrong?

    <target name="props">
        <property environment="env"/>
        <exec executable="cmd.exe">
          <arg line="/c set foo2=bar2"/>
        </exec>
        <echo message="foo2=${env.foo2}"/>
    </target>

Regards,
 Michael

-----Ursprüngliche Nachricht-----
Von: Broderick, Kevin [mailto:[EMAIL PROTECTED]]
Gesendet am: Mittwoch, 13. Februar 2002 15:33
An: Ant Users List
Betreff: RE: Setting Properties for Scripts

How about using the exec task to set and export your environment
variables ?
Regards
Kevin

-----Original Message-----
From: Koegel, Michael [mailto:[EMAIL PROTECTED]]
Sent: 13 February 2002 13:29
To: Ant Users List
Subject: AW: Setting Properties for Scripts


Hi,

life can be so simple ;-) That one worked fine.

But there is more to come:
Some of the 3rd-party-objects I use in the scripts read some values
from the system-environment.
How can I change the system environment from within my build.xml?
Using ANT_OPTS (-Dfoo=bar) works, but I would like to have everything in
my build.properties.

Regards,
 Michael


-----Ursprüngliche Nachricht-----
Von: Broderick, Kevin [mailto:[EMAIL PROTECTED]]
Gesendet am: Mittwoch, 13. Februar 2002 12:59
An: Ant Users List
Betreff: RE: Setting Properties for Scripts

Hi,
Not sure what you're trying to do, sounds a bit techie for me :)
How about the low tech approach ?
When you start your server (start-Target) why not touch a flag file
(ServerStarted.flg ?),
then when you want to know if the server has been started just use the
"available" task to check if it's there! You could delete it then when
you're stopping your server (stop-Target). I guess you could check if
it's there
and delete it in an "init" target when your script starts up ?

Regards
Kevin Broderick

-----Original Message-----
From: Koegel, Michael [mailto:[EMAIL PROTECTED]]
Sent: 13 February 2002 11:50
To: ANT User Mailinglist (E-Mail)
Subject: Setting Properties for Scripts


Hello,

I'm doing some jacl-Scripts in my build.xml for deployment. 
I want to check if the AppServer is running. If not I need to start it
and
remember that I did.
Then a test-target is run. After that the stop-Target needs to stop the
AppServer if it was started earlier.
How can I transfer this information from one target to another?
The only way I found is via System Properties like shown below.
Isn't there an easier way to do this?

<project name="Test JACL" default="env_test" basedir=".">

    <target name="env_test" depends="set_env, get_env">
            <property environment="env"/>
    </target>

    <target name="set_env">
        <property environment="env"/>
        <script language="jacl"> <![CDATA[
                package require java
                puts [java::call java.lang.System setProperty "foo"
"bar"]
        ]]> </script>
    </target>

    <target name="get_env">
        <property environment="env"/>
        <property name="foo" value="bar"/>
        <script language="jacl"> <![CDATA[
                package require java
                puts [java::call java.lang.System getProperty "foo"]
        ]]> </script>
    </target>
</project>

Kind Regards,
 Michael Kögel


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to