The problem with using for passwords is then you need a person
actually sitting there watching for the prompt. IIRC is smart
enough to see if the property is already bound, but that leads us back to
the original problem of how to bind that property in the first place.
--
Jeffrey E. Care ([EM
[EMAIL PROTECTED] wrote:
Then you need a system with a graphical user interface.
E.g. gump has not ...
CVS_HEAD skips the prompt if the property is set; I dont know if
the 1.6.x version does.
-steve
-
To unsubscribe, e-m
Then you need a system with a graphical user interface.
E.g. gump has not ...
Jan
>-Ursprüngliche Nachricht-
>Von: Patrick Martin [mailto:[EMAIL PROTECTED]
>Gesendet: Montag, 1. August 2005 13:51
>An: Ant Users List
>Betreff: Re: concealing passwords
>
>Hello,
&g
Hello,
You can also get the user input via an antform [1] UI which can star passwords:
Not tested, but something like that should work.
[1] http://antforms.sourceforge.net/
On 8/1/05, Steve Loughran <[EMAIL PROTECTED]> wrote:
> Roedy Green wrote:
> > I notice that in all the scripts I hav
Roedy Green wrote:
I notice that in all the scripts I have seen people just insert their
passwords as plain text in the scripts, e.g. for jarsigning.
I don't want to do that since I will be distributing the scripts along
with source code.
It seems there are several ways you could handle it:
In WebSphere we use a two-tier property file system:
*user.build.properties (located in $HOME) contains user specific
properties (such as passwords) and any local settings the user wishes to
override (such as whether to build the javadocs)
*build.properties (located in the source tree) contains
I notice that in all the scripts I have seen people just insert their
passwords as plain text in the scripts, e.g. for jarsigning.
I don't want to do that since I will be distributing the scripts
along with source code.
It seems there are several ways you could handle it:
1. put the password
