ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ballment, John" <>
Subject RE: Bug 46326 - StarTeam: Use Cache Agent for Checkouts
Date Fri, 06 Mar 2009 05:32:26 GMT

Hi Stefan,

Believe it or not I have at least one tester, Paul Coste.  He requested
some of the enhancments and gave suggested code.  I've tested/verified
his code and I've asked him to verify mine.

Sorry about the cases, in Starteam, setting cases to fixed only flags
that they need to go to UAT for verification and once successfully
validated the status is changed to Fixed Verified.  This then flags it
for a production release and once it is released the status goes to
Fixed Closed.

I guess my next question is, is it my responsibility to get distribute
these patches to some parties that are using Starteam and Ant to verify
or does it get added to the sandbox for others to checkout/build and


Pacific National Pty Ltd

John Ballment BIT(IS)
Senior Systems Analyst  
                       Phone: (02) 9893 2618 
                         Fax: (02) 9893 2698 
                        Mobile: 0418 740 871 
Level 4, 2-12 Macquarie Street 
Parramatta NSW 2150 Australia
-----Original Message-----
From: Stefan Bodewig [] 
Sent: Friday, 6 March 2009 16:13
Subject: Re: Bug 46326 - StarTeam: Use Cache Agent for Checkouts

Hi John

On 2009-03-06, Ballment, John <>

> I've integrated some patches from Paul Coste and added the following
> fixes:

> 39926 - StarTeam tasks to identify themselves as Ant + version number
> 40995 - StarTeam checkout support Promotion State
> 46326 - Use Cache Agent for Checkouts
> 46327 - Use cache credentials (optional) for logging in rather than 
> having scripts with hardcoded passwords

You shouldn't resolve any of these bugs in bugzilla before the patches
have actually been applied to Ant's code base - you lose visibility to
the committers.

> How quickly can we get these patches added to a build?

The main problem with many of the optional SCM tasks (among others) is
that no single Ant committer (still) has an environment around to
actually test it.

What we have now is your patch and your word that it works - and the
only test we have ourselves would be "it compiles".  If you could any
other Starteam user to test your patched version, it would help

Even then, you'd be bound to waiting for the next Ant release, which may
be several months away even if your patches were applied immediately.

A Starteam Antlib that could be released separately from Ant would be
the best option, but we'd have a hard time getting this released for the
same reasons that you have a hard time finding anybody to apply your
patch - no current committer could test the code.


To unsubscribe, e-mail: For additional
commands, e-mail:

This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.
Opinions, conclusions, views and other information in this 
that do not relate to the official business of Pacific National
are the views of the individual sender and shall be understood as
neither given nor endorsed by Pacific National.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message