Good - you got my meaning :-)
Jan
>-Ursprüngliche Nachricht-
>Von: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 9. August 2005 12:10
>An: Ant Developers List
>Betreff: RE: commons dev list CVS component
>
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>>
ATM tasks and types are declared via taskdefs/default.properties and
types/default.properties.
Could we extend that mechanism to allow an AntLib-URI?
taskdefs/default.properties
# standard ant tasks
mkdir=org.apache.tools.ant.taskdefs.Mkdir
jav
Von: Kev Jackson [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 9. August 2005 09:59
>An: Ant Developers List
>Betreff: Re: AW: AW: commons dev list CVS component
>
>[EMAIL PROTECTED] wrote:
>
>>Holding the source in an AntLib doesnt mean that we cant ship them in
>>
[EMAIL PROTECTED] wrote:
Holding the source in an AntLib doesnt mean that we cant ship them
in the "main" distro (nearly) as usual.
Jan
Indeed, we just need to make the task point to the re-packaged versions
instead, I presume we'll ship the svn task as part of verions 1.7 as an
antlib?
Holding the source in an AntLib doesnt mean that we cant ship them
in the "main" distro (nearly) as usual.
Jan
>-Ursprüngliche Nachricht-
>Von: Kev Jackson [mailto:[EMAIL PROTECTED]
>Gesendet: Dienstag, 9. August 2005 09:44
>An: Ant Developers List
>Betreff:
[EMAIL PROTECTED] wrote:
IMHO all stuff which relies on an external system (other than JDK or the OS :-)
should
be in an AntLib. And scm´s rely on the scm-server.
So a quick view on the core task list gave me:
- CVS: Cvs, CvsChangeLog, CvsVersion, CVSPass, CvsTagDiff
mmh - not more ...
And o
IMHO all stuff which relies on an external system (other than JDK or the OS :-)
should
be in an AntLib. And scm´s rely on the scm-server.
So a quick view on the core task list gave me:
- CVS: Cvs, CvsChangeLog, CvsVersion, CVSPass, CvsTagDiff
mmh - not more ...
And of course the optional stuff .
