[EMAIL PROTECTED]: Project svn-antlib-test (in module ant-antlibs) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project svn-antlib-test has an issue affecting its community integration. This issue affe

Re: VOTE ant-vss antlib promote to antlib proper

Kev Jackson wrote: On 1 Aug 2006, at 11:47, Alexey Solofnenko wrote: -0 Microsoft itself does not use it. Are we going to support already obsolete technology? Really? What is the new MS scm system or recommended scm system? I though VSS was basically the MS standard. MS never used VSS i

Re: VOTE ant-vss antlib promote to antlib proper

MS never used VSS internally. Do you think they are mad? They used to use something called SCUM and then I think went to ClearCase or Perforce. VSS is unreliable junk that doesnt scale and when it fails, fails big time with the entire history of files disappearing. Also its model of tagging

Re: VOTE ant-vss antlib promote to antlib proper

> I am +1 for moving VSS support into its own antlib. The only > problem is that adding the antlib to ANT_HOME/lib will not ensure > that existing build files will work, because to get the stuff > autoloaded, they need to declare it in a new namespace. Unless, > that is, the main defaults.properti

DO NOT REPLY [Bug 40152] New: - rmic: Ant 1.7 adds -vcompat when building iiop stubs

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 26618] - Relative path and file name parameters on XSLTProcess

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21042] - Setting XSL parameter to input filename when processed whole directory.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: VOTE ant-vss antlib promote to antlib proper

Hello, +1 with DDs views. Regards, Antoine Original-Nachricht Datum: Tue, 1 Aug 2006 08:04:57 -0500 Von: "Dominique Devienne" <[EMAIL PROTECTED]> An: "Ant Developers List" Betreff: Re: VOTE ant-vss antlib promote to antlib proper > > > I am +1 for moving VSS support into its

DO NOT REPLY [Bug 40157] New: - add a / task to add a host to known_hosts

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40157] - and Tasks to give meaningful errror messages

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: VOTE ant-vss antlib promote to antlib proper

On Mon, 31 Jul 2006, Alexey Solofnenko <[EMAIL PROTECTED]> wrote: > Microsoft itself has not been using Visual Source Safe for some > time. They recently productised their internal software as "Team > System". And released Visual Source Safe 2005 at almost the same time. Like it or not, VSS is g

Re: VOTE ant-vss antlib promote to antlib proper

On Tue, 1 Aug 2006, Dominique Devienne <[EMAIL PROTECTED]> wrote: > However, I'm not sure at all we should bind ourselves to moving > things to antlibs in a BC manner necessarily. +1 Stefan - To unsubscribe, e-mail: [EMAIL PROT

Re: VOTE ant-vss antlib promote to antlib proper

So, +1 on simply removing the vss entries to optional.properties, and provide the antlib. --DD What about the optional taskdef for VSS? If we want to release the VSS antlib, should we remove all the old VSS code from the core? This will definitely break working builds if someone upgrades a

Re: VOTE ant-vss antlib promote to antlib proper

On Wed, 2 Aug 2006, Kev Jackson <[EMAIL PROTECTED]> wrote: >> So, +1 on simply removing the vss entries to optional.properties, >> and provide the antlib. --DD > > What about the optional taskdef for VSS? If we want to release the > VSS antlib, should we remove all the old VSS code from the core?