One problem that I've had with Ant is that the logging facilities allow
directing the output to either the console or a log file, but typically
not both. This is fairly restrictive when you want to watch the
progress of a build and have an log of build that is identical to what
went by on the
The manual contains information about contributing in the section
Developing with Ant | Ant Task Guidelines
(http://ant.apache.org/ant_task_guidelines.html)
The tutorial Tasks using Properties Filesets uses that for
explaining how to contribute a new task. (document not finished yet)
But maybe
I tested last fridays head against cygwin last night on my
win machine.
I saw the JarTest and the JDepend failures but not the
AntLikeTasksAtTopLevelTest failure.
I looked into the JDepend error - it also happens in raw windows mode.
The problem
is strange - the encoding of the string got from
Hi,
I understand that there is a consensus to have macrodef use @{attribute}
notation.
I am not afraid that we cannot get committers support for local, I am more
afraid that in the course of introducing local, there will be more
discussions concerning issues of scope, thread support, ..., which
peterreilly2003/12/03 02:27:00
Modified:.build.xml
Log:
exclude jdepend test until dos problem with the test is sorted
Revision ChangesPath
1.402 +1 -0 ant/build.xml
Index: build.xml
bodewig 2003/12/03 02:32:57
Modified:src/etc/testcases/taskdefs/optional dotnet.xml
Log:
mono 0.29 on MacOS X works just fine
Revision ChangesPath
1.18 +0 -5 ant/src/etc/testcases/taskdefs/optional/dotnet.xml
Index: dotnet.xml
Antoine Levy-Lambert wrote:
Hi,
I understand that there is a consensus to have macrodef use @{attribute}
notation.
Well of the committers, there were 2 (you + Stefan) votes for it, + me
:-\ + jan via private e-mail.
I am not afraid that we cannot get committers support for local, I am more
peterreilly2003/12/03 02:37:36
Modified:.Tag: ANT_16_BRANCH build.xml
Log:
Sync with head
Revision ChangesPath
No revision
No revision
1.392.2.10 +1 -0 ant/build.xml
Index: build.xml
On Wed, 3 Dec 2003, Antoine Levy-Lambert [EMAIL PROTECTED] wrote:
I understand that there is a consensus to have macrodef use
@{attribute} notation.
Uhm, yes. If we count your is fine with me as +1, we have three +1s
which would be enough for lazy consensus.
My preference would be to turn
jhm 2003/12/03 03:25:04
Modified:docs/manual running.html
Log:
Add more system properties
Revision ChangesPath
1.25 +180 -7ant/docs/manual/running.html
Index: running.html
===
RCS file:
jhm 2003/12/03 03:25:39
Modified:docs/manual Tag: ANT_16_BRANCH running.html
Log:
Sync with HEAD
Revision ChangesPath
No revision
No revision
1.21.2.5 +179 -6ant/docs/manual/running.html
Index: running.html
peterreilly2003/12/03 05:16:01
Modified:.build.xml
docs/manual/CoreTasks macrodef.html
docs/manual/CoreTypes antlib.html
src/etc/testcases/taskdefs macrodef.xml
src/main/org/apache/tools/ant/taskdefs MacroDef.java
peterreilly2003/12/03 05:22:30
Modified:.Tag: ANT_16_BRANCH build.xml
docs/manual/CoreTasks Tag: ANT_16_BRANCH macrodef.html
docs/manual/CoreTypes Tag: ANT_16_BRANCH antlib.html
src/etc/testcases/taskdefs Tag: ANT_16_BRANCH
I have committed the changes to change from ${x} to @{x} for
macro attributes substitution.
Usage of macrodef is now as follows:
macrodef name=example
attribute name=x/
sequential
echoThe attribute has the value '@{x}'/echo
/sequential
/macrodef
This can be called as follows:
example x=a
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Sounds very very good. The light of the 1.6 release seems to come closer to
the horizon.
Cheers from Walldorf,
Antoine
-Ursprüngliche Nachricht-
Von: Peter Reilly [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 3. Dezember 2003 14:37
An: Ant Developers List; Ant Users List
Betreff:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
From: Peter Reilly [mailto:[EMAIL PROTECTED]
These changes will be available for the next ant 1.6 beta build.
+1 - sounds cool.
Let's crank out the next beta - is there anything else we are waiting for?
Conor
-
To
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
From: Conor MacNeill [mailto:[EMAIL PROTECTED]
From: Peter Reilly [mailto:[EMAIL PROTECTED]
These changes will be available for the next ant 1.6 beta build.
+1 - sounds cool.
Let's crank out the next beta - is there anything else we are
waiting for?
I am waiting for
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Thanks for the info Jan. I will review the docs you pointed me to and
likely put together a proper contribution a week or two.
Ron
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: December 3, 2003 12:58 AM
To: [EMAIL PROTECTED]
Subject: RE: TeeLogger
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24710.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24710.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi Jose,
I have dowloaded your jar file and run the build.xml, after having
downloaded saxon.
There are no errors for me.
Does this build.xml provoke exceptions or something like that on your site ?
Antoine
-Ursprungliche Nachricht-
Von: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED]
Hi Conor,
I would like to have a look at the failing testcases before releasing the
next beta, but it is going to be quick.
Cheers,
Antoine
-Ursprüngliche Nachricht-
Von: Conor MacNeill [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 3. Dezember 2003 15:06
An: Ant Developers List
Betreff:
On Thu, 4 Dec 2003, Conor MacNeill [EMAIL PROTECTED]
wrote:
Let's crank out the next beta
+1
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Antoine Lévy-Lambert wrote:
Hi Conor,
I would like to have a look at the failing testcases before releasing the
next beta, but it is going to be quick.
+1 sounds great.
Peter
Cheers,
Antoine
-Ursprüngliche Nachricht-
Von: Conor MacNeill [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 3.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25169.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25181.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
antoine 2003/12/03 13:58:08
Modified:src/testcases/org/apache/tools/ant BuildFileTest.java
Log:
1) make JarTest pass on Windows, these testcases were failing :
testRecreateWithUpdateNewerFile
testRecreateZipfilesetWithUpdateNewerFile,
the problem is the granularity of
antoine 2003/12/03 13:58:08
Modified:src/testcases/org/apache/tools/ant/taskdefs JarTest.java
Log:
1) make JarTest pass on Windows, these testcases were failing :
testRecreateWithUpdateNewerFile
testRecreateZipfilesetWithUpdateNewerFile,
the problem is the granularity
antoine 2003/12/03 13:58:07
Modified:.build.xml
Log:
1) make JarTest pass on Windows, these testcases were failing :
testRecreateWithUpdateNewerFile
testRecreateZipfilesetWithUpdateNewerFile,
the problem is the granularity of time stamps on the FAT
see
antoine 2003/12/03 14:06:41
Modified:.Tag: ANT_16_BRANCH build.xml
Log:
Merge from HEAD
1) make JarTest pass on Windows, these testcases were failing :
testRecreateWithUpdateNewerFile
testRecreateZipfilesetWithUpdateNewerFile,
the problem is the granularity
antoine 2003/12/03 14:06:41
Modified:src/testcases/org/apache/tools/ant/taskdefs Tag:
ANT_16_BRANCH JarTest.java
Log:
Merge from HEAD
1) make JarTest pass on Windows, these testcases were failing :
testRecreateWithUpdateNewerFile
antoine 2003/12/03 14:06:41
Modified:src/testcases/org/apache/tools/ant Tag: ANT_16_BRANCH
BuildFileTest.java
Log:
Merge from HEAD
1) make JarTest pass on Windows, these testcases were failing :
testRecreateWithUpdateNewerFile
OK I have fixed some problems, as usual rather simple.
I still have 3 testcases of
org.apache.tools.ant.taskdefs.AntLikeTasksAtTopLevelTest failing under
cygwin, but not under plain Windows.
I did not look at the guts of the test yet to find out what is wrong.
JDependTest has still 2 testcases
38 matches
Mail list logo
