perfsonar development work

[Roman Lapacz <>]

with more details:

The problem is in 'input' task. Example:

       <input message="Enter the home directory where the Java is 
installed (I need the home directory and not the directory where the 
executable binary is present) [/usr/local/jdk1.5.0]:"
           addproperty="java.path"
           defaultvalue="/usr/local/jdk1.5.0"
       />

Ant 1.6..x does not print value of defaultvalue attribute in brackets at 
the end of question so it must be added statically. Ant 1.7.x prints it.


Roman




Maciej Glowiak wrote:
> Hi Loukik,
>
> There is a problem with Ant. Using Ant 1.6.5 our scripts had to print 
> default values (those inside [ ] ), but since ver. 1.7.0 Ant does it 
> as well. So, using Ant 1.7.0 we have:
>
> ------------------------------------------------------------------------ 
>  Question Q [default]: [default]
> ------------------------------------------------------------------------
>   (one printed by script, second one by Ant)
>
> which of course may cause some problems or misunderstanding (see 
> Mario's e-mail with LS feedback on JRA1 Mailing List).
>
> Using long default values (usually paths) questions become difficult 
> to understand, like:
>
> ------------------------------------------------------------------------
> [input] Enter the path where you want to install the service [/home/mac/
> projects/perfsonar/new-structure/trunk/webapps]: [/home/mac/projects/per
> fsonar/new-structure/trunk/webapps]
> ------------------------------------------------------------------------
>
> But if we remove printing default values in our scripts at all, 
> somebody using old Ant 1.6.x won't see default values at all, like:
>
> ------------------------------------------------------------------------
>   Question Q:
> ------------------------------------------------------------------------
>
> So, there is a question whether to force users to use Ant 1.7.0 what 
> we did with Java some time ago (1.4 -> 1.5) and let ant print default 
> values for us. That's a question to Release Team, but also to 
> potential users who will need to upgrade Ant to 1.7.0 (I think some of 
> them already had it).
>
> By the way, Ant 1.7.0 fixed bug which we marked now as TO BE DONE 
> LATER --  See:  https://bugzilla.perfsonar.net/show_bug.cgi?id=123
>
> Maciej