date:20031203

TeeLogger class

2003-12-03 Thread Ron Coutts

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 console.  So in the spirit of the 'tee' command line
utility I've developed a TeeLogger class that extends DefaultLogger and
works a bit like MailLogger and a bit like XmlLogger.  It can direct log
output to two sinks simultaneously such as to the console and a file or
to two files at the same time (not that this latter feature is worth
much).

Here are some examples of specifying TeeLogger on the Ant command line:

ant -logger com.envistatech.tools.ant.TeeLogger  
Directs log output to console and log.txt by default.

ant -logger com.envistatech.tools.ant.TeeLogger
-DTeeLogger.file=mylog.txt
Directs log output to console and mylog.txt.

ant -logger com.envistatech.tools.ant.TeeLogger
-DTeeLogger.file=mylog.txt -logfile mylog2.txt
Directs log output to mylog.txt and mylog2.txt.


I think this might be useful to others and I wouldn't mind contributing
it.  So my questions are, is this a worthy contribution and if so what's
happens next?  This would be my first code contribution and I'm not at
all familiar with the process of contributing code.

Ron


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: TeeLogger class

2003-12-03 Thread Jan . Materne

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 the informations already present will help you.
http://cvs.apache.org/viewcvs.cgi/*checkout*/ant/docs/manual/tutorial-tasks-
filesets-properties.html?rev=1.2&content-type=text/plain#contribute


Directly to the first question in the "Contribute" area of the tutorial
   "is our task welcome? :-) Simply ask on the user list"

I thought for myself to implement a TeeLogger, so please contribute it :-)



Jan


> -Original Message-
> From: Ron Coutts [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 03, 2003 7:46 AM
> To: [EMAIL PROTECTED]
> Subject: TeeLogger class
> 
> 
> 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 console.  So in the spirit of the 'tee' command line
> utility I've developed a TeeLogger class that extends 
> DefaultLogger and
> works a bit like MailLogger and a bit like XmlLogger.  It can 
> direct log
> output to two sinks simultaneously such as to the console and 
> a file or
> to two files at the same time (not that this latter feature is worth
> much).
> 
> Here are some examples of specifying TeeLogger on the Ant 
> command line:
> 
> ant -logger com.envistatech.tools.ant.TeeLogger  
> Directs log output to console and log.txt by default.
> 
> ant -logger com.envistatech.tools.ant.TeeLogger
> -DTeeLogger.file=mylog.txt
> Directs log output to console and mylog.txt.
> 
> ant -logger com.envistatech.tools.ant.TeeLogger
> -DTeeLogger.file=mylog.txt -logfile mylog2.txt
> Directs log output to mylog.txt and mylog2.txt.
> 
> 
> I think this might be useful to others and I wouldn't mind 
> contributing
> it.  So my questions are, is this a worthy contribution and 
> if so what's
> happens next?  This would be my first code contribution and I'm not at
> all familiar with the process of contributing code.
> 
> Ron
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

Re: test failures in ant head

2003-12-03 Thread Peter Reilly

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 
BuildFileTest#getOutput() seems to
be incorrect - the string looks ok but it is twice as long as it should 
be and every second
character is not-printable.

I will disable the test for the moment.
Peter
Antoine Lévy-Lambert wrote:
While working on an improvement for regular expressions, I run the ant
testcases against ant head on Win2000/cygwin.
The results :
   [junit] Testcase:
testAnt(org.apache.tools.ant.taskdefs.AntLikeTasksAtTopLevelTest):  FAILED
   [junit] Testcase:
testSubant(org.apache.tools.ant.taskdefs.AntLikeTasksAtTopLevelTest):   FAILED
   [junit] Testcase:
testAntcall(org.apache.tools.ant.taskdefs.AntLikeTasksAtTopLevelTest):
FAILED
   [junit] TEST org.apache.tools.ant.taskdefs.AntLikeTasksAtTopLevelTest
FAILED
   [junit] Testcase:
testRecreateWithUpdateNewerFile(org.apache.tools.ant.taskdefs.JarTest):
FAILED
   [junit] Testcase:
testRecreateZipfilesetWithUpdateNewerFile(org.apache.tools.ant.taskdefs.JarT
est):   FAILED
   [junit] TEST org.apache.tools.ant.taskdefs.JarTest FAILED
   [junit] TEST org.apache.tools.ant.taskdefs.optional.XalanLiaisonTest
FAILED
   [junit] TEST org.apache.tools.ant.taskdefs.optional.XslpLiaisonTest
FAILED
   [junit] Testcase:
testSimple(org.apache.tools.ant.taskdefs.optional.jdepend.JDependTest):
FAILED
   [junit] Testcase:
testXml(org.apache.tools.ant.taskdefs.optional.jdepend.JDependTest):FAILED
   [junit] Testcase:
testForkXml(org.apache.tools.ant.taskdefs.optional.jdepend.JDependTest):
FAILED
   [junit] TEST org.apache.tools.ant.taskdefs.optional.jdepend.JDependTest
FAILED
Hopefully the failures are more due to cygwin or to misconfigurations rather
than anything else.
Looks like there are some details to be checked.
Cheers,
Antoine

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: Ant 1.6 local and ThreadLocals

2003-12-03 Thread Antoine Levy-Lambert

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 will
further delay the release of 1.6.

My preference would be to turn macrodef to use @{attribute} for 1.6 and
delay local for 1.7.

Peter, how soon can you deliver the @{attribute} change ?

I would like the following scenario :

- introduce @{attribute} in 1.6 and in HEAD,
- fix failing testcases
- deliver a beta3
- introduce local in HEAD
- deliver ant 1.6

Cheers,

Antoine

-Ursprungliche Nachricht-
Von: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 2. Dezember 2003 16:20
An: [EMAIL PROTECTED]
Betreff: Re: Ant 1.6 local and ThreadLocals

On Mon, 1 Dec 2003, Jose Alberto Fernandez <[EMAIL PROTECTED]>
wrote:

> Well now that we are finally getting to an agreement
> on  I think it is time to start a new round
> of rocous over , (not enough traffic today ;-P )

We don't seem to be too successful in generating responses these
days. 8-)

I'm a bit torn between releasing 1.6 without any local support and
trying to get enough support for it to delay 1.6 further.  I think
local is necessary to make macrodef as powerful as it should be, but
wouldn't want to wait another two months to finally get committer
support for it into 1.6.

> I still fill a little unconfortable on using 
> for defining local-scopes (which was the original usage)
> and using  to define values that must be different
> on different threads of execution (i.e., Java ThreadLocals).

Hmm,

  ...

  ...

should give something predictable - or something that is completely
undefined, much like what we'd currently have for references.

The above looks like a "user's fault" situation, until you let
's using s into the game.

   ...

with multiple invocations of  inside .  For a scenario
like this,  implicitly promises to be Thread local.  At least
it does for me.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant build.xml

2003-12-03 Thread peterreilly

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
  ===
  RCS file: /home/cvs/ant/build.xml,v
  retrieving revision 1.401
  retrieving revision 1.402
  diff -u -r1.401 -r1.402
  --- build.xml 24 Oct 2003 10:16:16 -  1.401
  +++ build.xml 3 Dec 2003 10:27:00 -   1.402
  @@ -328,6 +328,7 @@
   
 
   
  +

cvs commit: ant/src/etc/testcases/taskdefs/optional dotnet.xml

2003-12-03 Thread bodewig

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
  ===
  RCS file: /home/cvs/ant/src/etc/testcases/taskdefs/optional/dotnet.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- dotnet.xml25 Nov 2003 09:16:57 -  1.17
  +++ dotnet.xml3 Dec 2003 10:32:57 -   1.18
  @@ -90,15 +90,10 @@
   dotnetapps.found=${dotnetapps.found}
   
  
  -  
  -
  -  
  -
   
 
 
   
  -  
  
  
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AW: Ant 1.6 local and ThreadLocals

2003-12-03 Thread Peter Reilly

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
afraid that in the course of introducing local, there will be more
discussions concerning issues of scope, thread support, ..., which will
further delay the release of 1.6.
My preference would be to turn macrodef to use @{attribute} for 1.6 and
delay local for 1.7.
 

This would be my feeling as well - maybe have local for 1.6.1 if necessary.
Peter, how soon can you deliver the @{attribute} change ?
 

It is ready now to commit. :-)
Peter
I would like the following scenario :
- introduce @{attribute} in 1.6 and in HEAD,
- fix failing testcases
- deliver a beta3
- introduce local in HEAD
- deliver ant 1.6
Cheers,
Antoine
-Ursprungliche Nachricht-
Von: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 2. Dezember 2003 16:20
An: [EMAIL PROTECTED]
Betreff: Re: Ant 1.6 local and ThreadLocals
On Mon, 1 Dec 2003, Jose Alberto Fernandez <[EMAIL PROTECTED]>
wrote:
 

Well now that we are finally getting to an agreement
on  I think it is time to start a new round
of rocous over , (not enough traffic today ;-P )
   

We don't seem to be too successful in generating responses these
days. 8-)
I'm a bit torn between releasing 1.6 without any local support and
trying to get enough support for it to delay 1.6 further.  I think
local is necessary to make macrodef as powerful as it should be, but
wouldn't want to wait another two months to finally get committer
support for it into 1.6.
 

I still fill a little unconfortable on using 
for defining local-scopes (which was the original usage)
and using  to define values that must be different
on different threads of execution (i.e., Java ThreadLocals).
   

Hmm,

 
   
 ...
   
 
 
   
 ...
   
 

should give something predictable - or something that is completely
undefined, much like what we'd currently have for references.
The above looks like a "user's fault" situation, until you let
's using s into the game.

 
   
  ...
   
 

with multiple invocations of  inside .  For a scenario
like this,  implicitly promises to be Thread local.  At least
it does for me.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant build.xml

2003-12-03 Thread peterreilly

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
  ===
  RCS file: /home/cvs/ant/build.xml,v
  retrieving revision 1.392.2.9
  retrieving revision 1.392.2.10
  diff -u -r1.392.2.9 -r1.392.2.10
  --- build.xml 30 Oct 2003 16:21:31 -  1.392.2.9
  +++ build.xml 3 Dec 2003 10:37:36 -   1.392.2.10
  @@ -327,6 +327,7 @@
   
 
   
  +

Re: Ant 1.6 local and ThreadLocals

2003-12-03 Thread Stefan Bodewig

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 macrodef to use @{attribute} for 1.6
> and delay local for 1.7.

Works for me.

I could also get convinced that we could introduce it in a 1.6.1
release.

> I would like the following scenario :
> 
> - introduce @{attribute} in 1.6 and in HEAD,
> - fix failing testcases
> - deliver a beta3
> - introduce local in HEAD
> - deliver ant 1.6

+1

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant/docs/manual running.html

2003-12-03 Thread jhm

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: /home/cvs/ant/docs/manual/running.html,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- running.html  28 Nov 2003 11:56:29 -  1.24
  +++ running.html  3 Dec 2003 11:25:04 -   1.25
  @@ -213,12 +213,185 @@
   
   
   Java System Properties
  -Some of Ants core classes can be configured via system properties:
  -
  -  org.apache.tools.ant.ProjectHelper - specifies the
  -  classname to use as ProjectHelper. The class must extend 
org.apache.tools.ant.ProjectHelper.
  -  If not set org.apache.tools.ant.ProjectHelper is used as 
ProjectHelper.
  -
  +Some of Ants core classes ant tasks can be configured via system 
properties.
  +So here the result of a search through the codebase. Because system 
properties are
  +available via Project instance, I searched for them with a
  +
  +grep -r -n "getPropert" * > ..\grep.txt
  +
  +command. After that I filtered out the often-used but not-so-important 
values (most of them
  +read-only values): path.separator, ant.home, basedir, user.dir, os.name, 
ant.file,
  +line.separator, java.home, java.version, java.version, user.home, 
java.class.path
  +And I filtered out the getPropertyHelper access.
  +
  +
  +  property name
  +  valid values /default value
  +  description
  +
  +
  +  ant.input.properties
  +  filename (required)
  +  Name of the file holding the values for the
  +  PropertyFileInputHandler.
  +  
  +
  +
  +  ant.logger.defaults
  +  
  +  filename (optional, default '/org/ apache/ tools/ ant/ listener/ 
defaults.properties')
  +  Name of the file holding the color mappings for the
  +  AnsiColorLogger.
  +  
  +
  +
  +  ant.netrexxc.*
  +  several formats
  +  Use specified values as defaults for netrexxc.
  +  
  +
  +
  +  ant.PropertyHelper
  +  ant-reference-name (optional)
  +  Specify the PropertyHelper to use. The object must be of the type
  +  org.apache.tools.ant.PropertyHelper. If not defined an object of
  +  org.apache.tools.ant.PropertyHelper will be used as PropertyHelper.
  +  
  +
  +
  +  ant.regexp.regexpimpl
  +  classname
  +  classname for a RegExp implementation; if not set Ant tries to
  +  find another (Jdk14, Oro...);
  +  RegExp-Mapper
  +  "Choice of regular expression implementation"
  +  
  +
  +
  +  ant.reuse.loader
  +  boolean
  +  allow to reuse classloaders
  +  used in org.apache.tools.ant.util.ClasspathUtil
  +  
  +
  +
  +  ant.XmlLogger.stylesheet.uri
  +  filename (default 'log.xsl')
  +  Name for the stylesheet to include in the logfile by
  +  XmlLogger.
  +  
  +
  +
  +  build.compiler
  +  name
  +  Specify the default compiler to use.
  +  see javac,
  +  EJB Tasks
  +  (compiler attribute),
  +  IContract,
  +  javah
  +  
  +
  +
  +  build.compiler.emacs
  +  boolean (default false)
  +  Enable emacs-compatible error messages.
  +  see javac "Jikes Notes"
  +  
  +
  +
  +  build.compiler.fulldepend
  +  boolean (default false)
  +  Enable full dependency checking
  +  see javac "Jikes Notes"
  +  
  +
  +
  +  build.compiler.jvc.extensions
  +  boolean (default true)
  +  enable Microsoft extensions of their java compiler
  +  see javac "Jvc Notes"
  +  
  +
  +
  +  build.compiler.pedantic
  +  boolean (default false)
  +  Enable pedantic warnings.
  +  see javac "Jikes Notes"
  +  
  +
  +
  +  build.compiler.warnings
  +  Deprecated flag
  +   see javac "Jikes Notes" 
  +
  +
  +  build.rmic
  +  name
  +  control the rmic compiler 
  +
  +
  +  build.sysclasspath
  +  "only", something else
  +  only: current threads get the actual class loader
  +  (AntClassLoader.setThreadContextLoader()).
  +  else: use core loader as default (ComponentHelper.initTasks()). Disable
  +  changing the classloader (oata.taskdefs.Classloader.execute() 
experimental
  +  task).
  +  
  +  
  +
  +
  +  file.encoding
  +  name of a supported character set (e.g. UTF-8, ISO-8859-1, 
US-ASCII)
  +  use as default character set of email messages; use as default for 
source-, dest- and bundleencoding
  +  in translate 
  +  see JavaDoc of http://java.sun.com/j2se/1.4.2/docs/api/java/nio/charset/Charset.html";>java.nio.charset.Charset
  +  for more information about character sets (not used in Ant, but has 
nice docs).
  +  
  +
  +
  +  jikes.class.path
  +  path
  +  The specified path is added to the classpath if jikes is used as 
compiler.
  +
  +
  +  MailLogger.properties.file, MailLogger.*
  +  filename (optional, defaults derived from Project instance)
  +  Name of the file holding properties for sending emails by the
  +  MailLogger. Override 
prope

cvs commit: ant/docs/manual running.html

2003-12-03 Thread jhm

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
  ===
  RCS file: /home/cvs/ant/docs/manual/running.html,v
  retrieving revision 1.21.2.4
  retrieving revision 1.21.2.5
  diff -u -r1.21.2.4 -r1.21.2.5
  --- running.html  28 Nov 2003 12:01:02 -  1.21.2.4
  +++ running.html  3 Dec 2003 11:25:39 -   1.21.2.5
  @@ -212,12 +212,185 @@
   
   
   Java System Properties
  -Some of Ants core classes can be configured via system properties:
  -
  -  org.apache.tools.ant.ProjectHelper - specifies the
  -  classname to use as ProjectHelper. The class must extend 
org.apache.tools.ant.ProjectHelper.
  -  If not set org.apache.tools.ant.ProjectHelper is used as 
ProjectHelper.
  -
  +Some of Ants core classes ant tasks can be configured via system 
properties.
  +So here the result of a search through the codebase. Because system 
properties are
  +available via Project instance, I searched for them with a
  +
  +grep -r -n "getPropert" * > ..\grep.txt
  +
  +command. After that I filtered out the often-used but not-so-important 
values (most of them
  +read-only values): path.separator, ant.home, basedir, user.dir, os.name, 
ant.file,
  +line.separator, java.home, java.version, java.version, user.home, 
java.class.path
  +And I filtered out the getPropertyHelper access.
  +
  +
  +  property name
  +  valid values /default value
  +  description
  +
  +
  +  ant.input.properties
  +  filename (required)
  +  Name of the file holding the values for the
  +  PropertyFileInputHandler.
  +  
  +
  +
  +  ant.logger.defaults
  +  
  +  filename (optional, default '/org/ apache/ tools/ ant/ listener/ 
defaults.properties')
  +  Name of the file holding the color mappings for the
  +  AnsiColorLogger.
  +  
  +
  +
  +  ant.netrexxc.*
  +  several formats
  +  Use specified values as defaults for netrexxc.
  +  
  +
  +
  +  ant.PropertyHelper
  +  ant-reference-name (optional)
  +  Specify the PropertyHelper to use. The object must be of the type
  +  org.apache.tools.ant.PropertyHelper. If not defined an object of
  +  org.apache.tools.ant.PropertyHelper will be used as PropertyHelper.
  +  
  +
  +
  +  ant.regexp.regexpimpl
  +  classname
  +  classname for a RegExp implementation; if not set Ant tries to
  +  find another (Jdk14, Oro...);
  +  RegExp-Mapper
  +  "Choice of regular expression implementation"
  +  
  +
  +
  +  ant.reuse.loader
  +  boolean
  +  allow to reuse classloaders
  +  used in org.apache.tools.ant.util.ClasspathUtil
  +  
  +
  +
  +  ant.XmlLogger.stylesheet.uri
  +  filename (default 'log.xsl')
  +  Name for the stylesheet to include in the logfile by
  +  XmlLogger.
  +  
  +
  +
  +  build.compiler
  +  name
  +  Specify the default compiler to use.
  +  see javac,
  +  EJB Tasks
  +  (compiler attribute),
  +  IContract,
  +  javah
  +  
  +
  +
  +  build.compiler.emacs
  +  boolean (default false)
  +  Enable emacs-compatible error messages.
  +  see javac "Jikes Notes"
  +  
  +
  +
  +  build.compiler.fulldepend
  +  boolean (default false)
  +  Enable full dependency checking
  +  see javac "Jikes Notes"
  +  
  +
  +
  +  build.compiler.jvc.extensions
  +  boolean (default true)
  +  enable Microsoft extensions of their java compiler
  +  see javac "Jvc Notes"
  +  
  +
  +
  +  build.compiler.pedantic
  +  boolean (default false)
  +  Enable pedantic warnings.
  +  see javac "Jikes Notes"
  +  
  +
  +
  +  build.compiler.warnings
  +  Deprecated flag
  +   see javac "Jikes Notes" 
  +
  +
  +  build.rmic
  +  name
  +  control the rmic compiler 
  +
  +
  +  build.sysclasspath
  +  "only", something else
  +  only: current threads get the actual class loader
  +  (AntClassLoader.setThreadContextLoader()).
  +  else: use core loader as default (ComponentHelper.initTasks()). Disable
  +  changing the classloader (oata.taskdefs.Classloader.execute() 
experimental
  +  task).
  +  
  +  
  +
  +
  +  file.encoding
  +  name of a supported character set (e.g. UTF-8, ISO-8859-1, 
US-ASCII)
  +  use as default character set of email messages; use as default for 
source-, dest- and bundleencoding
  +  in translate 
  +  see JavaDoc of http://java.sun.com/j2se/1.4.2/docs/api/java/nio/charset/Charset.html";>java.nio.charset.Charset
  +  for more information about character sets (not used in Ant, but has 
nice docs).
  +  
  +
  +
  +  jikes.class.path
  +  path
  +  The specified path is added to the classpath if jikes is used as 
compiler.
  +
  +
  +  MailLogger.properties.file, MailLogger.*
  +  filename (optional, defaults derived from Project instance)
  +  Nam

cvs commit: ant/src/testcases/org/apache/tools/ant/taskdefs MacroDefTest.java

2003-12-03 Thread peterreilly

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
MacroInstance.java
   src/testcases/org/apache/tools/ant/taskdefs
MacroDefTest.java
  Log:
  Change ${x} to @{x} for attribute notation of macrodef
  
  Revision  ChangesPath
  1.403 +2 -2  ant/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/ant/build.xml,v
  retrieving revision 1.402
  retrieving revision 1.403
  diff -u -r1.402 -r1.403
  --- build.xml 3 Dec 2003 10:27:00 -   1.402
  +++ build.xml 3 Dec 2003 13:16:01 -   1.403
  @@ -817,10 +817,10 @@
   
 
 
  -
  -  
  +  
   
 
   
  
  
  
  1.6   +22 -13ant/docs/manual/CoreTasks/macrodef.html
  
  Index: macrodef.html
  ===
  RCS file: /home/cvs/ant/docs/manual/CoreTasks/macrodef.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- macrodef.html 31 Oct 2003 09:51:24 -  1.5
  +++ macrodef.html 3 Dec 2003 13:16:01 -   1.6
  @@ -3,6 +3,11 @@
 
   
   MacroDef Task
  +
  +  
  +
 
   
 
  @@ -49,8 +54,12 @@
   
   
 This attribute is placed in the body of the templated
  -  task using the ant property notation - ${attribute name}.
  -  Note that is not an actual ant property.
  +  task using a notation similar to the ant property notation
  +  - @{attribute name}. (May be remembered as "put the substitution
  +  AT this location").
  +  The escape sequence @@{x} is used to allow @{x} to be
  +  placed in the text without substitution of x.
  +  This corresponds to the $${x} escape sequence for properties
   
   Parameters
   
  @@ -107,12 +116,12 @@
 runs it.
   
   
  -  
  +
   
  
  
  
  -  v is ${v}
  +  v is @{v}
 
  
   
  @@ -122,7 +131,7 @@
 this is a test
  
   
  -  
  +
   
   
 The following fragment defines a task called  which
  @@ -132,29 +141,29 @@
 http://ant-contrib.sourceforge.net/";>ant-contrib project.
   
   
  -  
  +
   
  
  
  
  
  
  -  
  -  
  - 
  +  
  +  
  + 
   
   

 
   
  -  
  +
   
   
 This then can be used as follows:
   
   
  -  
  +
   
  
  @@ -165,7 +174,7 @@
 
  
   
  -  
  +
   
   
   Copyright © 2003 Apache Software
  
  
  
  1.7   +2 -2  ant/docs/manual/CoreTypes/antlib.html
  
  Index: antlib.html
  ===
  RCS file: /home/cvs/ant/docs/manual/CoreTypes/antlib.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- antlib.html   18 Nov 2003 10:51:41 -  1.6
  +++ antlib.html   3 Dec 2003 13:16:01 -   1.7
  @@ -89,7 +89,7 @@
 
 
  
  -ls -Rl ${dir}
  +ls -Rl @{dir}

 
  
  @@ -132,7 +132,7 @@
 
 

  -
  +
   
  
   
  
  
  
  1.5   +14 -4 ant/src

cvs commit: ant/src/testcases/org/apache/tools/ant/taskdefs MacroDefTest.java

2003-12-03 Thread peterreilly

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 macrodef.xml
   src/main/org/apache/tools/ant/taskdefs Tag: ANT_16_BRANCH
MacroDef.java MacroInstance.java
   src/testcases/org/apache/tools/ant/taskdefs Tag:
ANT_16_BRANCH MacroDefTest.java
  Log:
  Sync with HEAD
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.392.2.11 +2 -2  ant/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/ant/build.xml,v
  retrieving revision 1.392.2.10
  retrieving revision 1.392.2.11
  diff -u -r1.392.2.10 -r1.392.2.11
  --- build.xml 3 Dec 2003 10:37:36 -   1.392.2.10
  +++ build.xml 3 Dec 2003 13:22:29 -   1.392.2.11
  @@ -816,10 +816,10 @@
   
 
 
  -
  -  
  +  
   
 
   
  
  
  
  No   revision
  No   revision
  1.2.2.5   +22 -13ant/docs/manual/CoreTasks/macrodef.html
  
  Index: macrodef.html
  ===
  RCS file: /home/cvs/ant/docs/manual/CoreTasks/macrodef.html,v
  retrieving revision 1.2.2.4
  retrieving revision 1.2.2.5
  diff -u -r1.2.2.4 -r1.2.2.5
  --- macrodef.html 31 Oct 2003 09:56:42 -  1.2.2.4
  +++ macrodef.html 3 Dec 2003 13:22:30 -   1.2.2.5
  @@ -4,6 +4,11 @@
   
   MacroDef Task
   
  +
  +  
  +
 
   
 
  @@ -50,8 +55,12 @@
   
   
 This attribute is placed in the body of the templated
  -  task using the ant property notation - ${attribute name}.
  -  Note that is not an actual ant property.
  +  task using a notation similar to the ant property notation
  +  - @{attribute name}. (May be remembered as "put the substitution
  +  AT this location").
  +  The escape sequence @@{x} is used to allow @{x} to be
  +  placed in the text without substitution of x.
  +  This corresponds to the $${x} escape sequence for properties
   
   Parameters
   
  @@ -108,12 +117,12 @@
 runs it.
   
   
  -  
  +
   
  
  
  
  -  v is ${v}
  +  v is @{v}
 
  
   
  @@ -123,7 +132,7 @@
 this is a test
  
   
  -  
  +
   
   
 The following fragment defines a task called  which
  @@ -133,29 +142,29 @@
 http://ant-contrib.sourceforge.net/";>ant-contrib project.
   
   
  -  
  +
   
  
  
  
  
  
  -  
  -  
  - 
  +  
  +  
  + 
   
   

 
   
  -  
  +
   
   
 This then can be used as follows:
   
   
  -  
  +
   
  
  @@ -166,7 +175,7 @@
 
  
   
  -  
  +
   
   
   Copyright © 2003 Apache Software
  
  
  
  No   revision
  No   revision
  1.3.2.5   +2 -2  ant/docs/manual/CoreTypes/antlib.html
  
  Index: antlib.html
  ===
  RCS file: /home/cvs/ant/docs/manual/CoreTypes/antlib.html,v
  retrieving revision 1.3.2.4
  retrieving revision 1.3.2.5
  diff -u -r1.3.2.4 -r1.3.2.5
  --- antlib.html   18 Nov 2003 11:29:06 -  1.3.2.4
  +++ antlib.html   3 Dec 2003 13:22:30 -   1.3.2.5
  @@ -90,7 +90,7 @@
 
 
  
  -ls -Rl ${dir}
  +ls -Rl @{dir}

Macrodef @{x}

2003-12-03 Thread Peter Reilly

I have committed the changes to change from ${x} to @{x} for
macro attributes substitution.
Usage of macrodef is now as follows:

  
  
 The attribute has the value '@{x}'
 

This can be called as follows:

The escape sequence @@{ may be used to escape the substitution:

  
  
 The attribute @@{x} has the value '@{x}'
 


Will result in:
[echo] The attribute @{x} has the value 'a value'
The mechanisms for substition are different for properties and
macrodef attributes so one may now do the following:
   
 
 
   @@{prop} is '@{prop}', value of [EMAIL PROTECTED] is 
'[EMAIL PROTECTED]'
 
   
   
   

resulting in:
[echo] @{prop} is 'property', value of ${property} is 'A property 
value'

These changes will be available for the next ant 1.6 beta build.
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25163] New: - Unzip: java.io.IOException: Negative seek offset

2003-12-03 Thread bugzilla

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://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163

Unzip: java.io.IOException: Negative seek offset

   Summary: Unzip: java.io.IOException: Negative seek offset
   Product: Ant
   Version: 1.6Beta
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Critical
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I have a textfile x.txt on a server:
SunOS aserver 5.9 Generic_112233-08 sun4us sparc FJSV,GPUS

I use gzip 1.3 (1999-12-21) to zip it. The file becomes x.txt.gz

Through FTP I download the file binary to my PC (Win 2000 Professional).

I run in a task only the following:


When running only this task, I get:

C:\dvl.home\prj\ksz\build.xml:223: Error while expanding 
C:\jtemp\zipped\x.txt.gz
at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:169)
at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:133)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:302)
at org.apache.tools.ant.Task.perform(Task.java:401)
at org.apache.tools.ant.Target.execute(Target.java:338)
at org.apache.tools.ant.Target.performTasks(Target.java:365)
at org.apache.tools.ant.Project.executeTarget(Project.java:1237)
at org.apache.tools.ant.Project.executeTargets(Project.java:1094)
at org.apache.tools.ant.Main.runBuild(Main.java:669)
at org.apache.tools.ant.Main.startAnt(Main.java:220)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:215)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:90)
--- Nested Exception ---
java.io.IOException: Negative seek offset
at java.io.RandomAccessFile.seek(Native Method)
at org.apache.tools.zip.ZipFile.positionAtCentralDirectory
(ZipFile.java:396)
at org.apache.tools.zip.ZipFile.populateFromCentralDirectory
(ZipFile.java:274)
at org.apache.tools.zip.ZipFile.(ZipFile.java:180)
at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:158)
at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:133)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:302)
at org.apache.tools.ant.Task.perform(Task.java:401)
at org.apache.tools.ant.Target.execute(Target.java:338)
at org.apache.tools.ant.Target.performTasks(Target.java:365)
at org.apache.tools.ant.Project.executeTarget(Project.java:1237)
at org.apache.tools.ant.Project.executeTargets(Project.java:1094)
at org.apache.tools.ant.Main.runBuild(Main.java:669)
at org.apache.tools.ant.Main.startAnt(Main.java:220)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:215)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:90)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: Macrodef @{x}

2003-12-03 Thread Antoine Lévy-Lambert

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: Macrodef @{x}


I have committed the changes to change from ${x} to @{x} for
macro attributes substitution.

Usage of macrodef is now as follows:

   
   
  The attribute has the value '@{x}'
  


This can be called as follows:


The escape sequence @@{ may be used to escape the substitution:


   
   
  The attribute @@{x} has the value '@{x}'
  




Will result in:
 [echo] The attribute @{x} has the value 'a value'

The mechanisms for substition are different for properties and
macrodef attributes so one may now do the following:


  
  
@@{prop} is '@{prop}', value of [EMAIL PROTECTED] is
'[EMAIL PROTECTED]'
  




resulting in:
 [echo] @{prop} is 'property', value of ${property} is 'A property
value'

These changes will be available for the next ant 1.6 beta build.

Peter

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25163] - Unzip: java.io.IOException: Negative seek offset

2003-12-03 Thread bugzilla

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://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163

Unzip: java.io.IOException: Negative seek offset





--- Additional Comments From [EMAIL PROTECTED]  2003-12-03 13:59 ---
The task gunzip works well in this case but I my situation I can't use gunzip 
because I want to use filesets: all the .gz-files in my directory have to be 
uncompressed.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Macrodef @{x}

2003-12-03 Thread Conor MacNeill

> 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 unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25163] - Unzip: java.io.IOException: Negative seek offset

2003-12-03 Thread bugzilla

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://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163

Unzip: java.io.IOException: Negative seek offset

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-12-03 14:07 ---
This is not a bug.
You are using the incorrect uncompression method.
You need to use  instead of .
 will think that this is a zip file and
not a gzip file.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Macrodef @{x}

2003-12-03 Thread Jose Alberto Fernandez

> 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 some bugs in the XMLCatalogue that I submitted.
Has anyone has a chance to look at that?

Jose Alberto

> Conor
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25163] - Unzip: java.io.IOException: Negative seek offset

2003-12-03 Thread bugzilla

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://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163

Unzip: java.io.IOException: Negative seek offset





--- Additional Comments From [EMAIL PROTECTED]  2003-12-03 14:18 ---
Ikkk.
You are right, the guzip task does not
take a fileset !
And one cannot set the compression method for
unzip or use the untar task.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25163] - Unzip: java.io.IOException: Negative seek offset

2003-12-03 Thread bugzilla

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://nagoya.apache.org/bugzilla/show_bug.cgi?id=25163

Unzip: java.io.IOException: Negative seek offset





--- Additional Comments From [EMAIL PROTECTED]  2003-12-03 14:33 ---
As a work-around (and when ant 1.6 beta3 comes out soon..)
you can use  from ant-contrib, (for is like foreach
but it uses macrodef instead of antcall so it is currently faster
for each iteration).

  


  

  
  

  

  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: TeeLogger class

2003-12-03 Thread Ron Coutts

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 class
> 
> 
> 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 the informations already present will 
> help you.
> http://cvs.apache.org/viewcvs.cgi/*checkout*/ant/docs/manual/t
> utorial-tasks-
> filesets-properties.html?rev=1.2&content-type=text/plain#contribute
> 
> 
> Directly to the first question in the "Contribute" area of 
> the tutorial
>"is our task welcome? :-) Simply ask on the user list"
> 
> I thought for myself to implement a TeeLogger, so please 
> contribute it :-)
> 
> 
> 
> Jan
> 
> 
> > -Original Message-
> > From: Ron Coutts [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, December 03, 2003 7:46 AM
> > To: [EMAIL PROTECTED]
> > Subject: TeeLogger class
> > 
> > 
> > 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 console.  So in the spirit of the 'tee' command line
> > utility I've developed a TeeLogger class that extends 
> > DefaultLogger and
> > works a bit like MailLogger and a bit like XmlLogger.  It can 
> > direct log
> > output to two sinks simultaneously such as to the console and 
> > a file or
> > to two files at the same time (not that this latter feature is worth
> > much).
> > 
> > Here are some examples of specifying TeeLogger on the Ant
> > command line:
> > 
> > ant -logger com.envistatech.tools.ant.TeeLogger
> > Directs log output to console and log.txt by default.
> > 
> > ant -logger com.envistatech.tools.ant.TeeLogger
> > -DTeeLogger.file=mylog.txt
> > Directs log output to console and mylog.txt.
> > 
> > ant -logger com.envistatech.tools.ant.TeeLogger
> > -DTeeLogger.file=mylog.txt -logfile mylog2.txt
> > Directs log output to mylog.txt and mylog2.txt.
> > 
> > 
> > I think this might be useful to others and I wouldn't mind
> > contributing
> > it.  So my questions are, is this a worthy contribution and 
> > if so what's
> > happens next?  This would be my first code contribution and 
> I'm not at
> > all familiar with the process of contributing code.
> > 
> > Ron
> > 
> > 
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 24710] - task (not )

2003-12-03 Thread bugzilla

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://nagoya.apache.org/bugzilla/show_bug.cgi?id=24710

 task (not )





--- Additional Comments From [EMAIL PROTECTED]  2003-12-03 16:12 ---
Will ant-contrib's  also adopt @{} attribute notation?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 24710] - task (not )

2003-12-03 Thread bugzilla

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://nagoya.apache.org/bugzilla/show_bug.cgi?id=24710

 task (not )





--- Additional Comments From [EMAIL PROTECTED]  2003-12-03 16:19 ---
Yes,
It uses the macrodef task as a basis for the iteration.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: Macrodef @{x}

2003-12-03 Thread Antoine Levy-Lambert

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]
Gesendet: Mittwoch, 3. Dezember 2003 15:17
An: Ant Developers List
Betreff: RE: Macrodef @{x}


> 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 some bugs in the XMLCatalogue that I submitted.
Has anyone has a chance to look at that?

Jose Alberto

> Conor
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: Macrodef @{x}

2003-12-03 Thread Antoine Lévy-Lambert

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: RE: Macrodef @{x}


> 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 unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Macrodef @{x}

2003-12-03 Thread Stefan Bodewig

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]

Re: AW: Macrodef @{x}

2003-12-03 Thread Peter Reilly

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. Dezember 2003 15:06
An: Ant Developers List
Betreff: RE: Macrodef @{x}
 

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 unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25169] New: - Property file specified from command line doesn't expand all properties

2003-12-03 Thread bugzilla

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://nagoya.apache.org/bugzilla/show_bug.cgi?id=25169

Property file specified from command line doesn't expand all properties

   Summary: Property file specified from command line doesn't expand
all properties
   Product: Ant
   Version: 1.5.4
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Apache Ant version 1.5.4 compiled on August 12 2003
Red Hat Linux, J2SE 1.4

Consider following build.properties file:
base.path=/usr/local
base.file=${base.path}/abc.txt

and build.xml:








${xyz} is printed correctly as /usr/local//abc.txt

Now remove  from buil.xml and run:
ant -propertyfile build.properties

${xyz} is now printed as
${base.path}/abc.txt

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25181] New: - SYMLINK task creates cyclic symlinks

2003-12-03 Thread bugzilla

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://nagoya.apache.org/bugzilla/show_bug.cgi?id=25181

SYMLINK task creates cyclic symlinks

   Summary: SYMLINK task creates cyclic symlinks
   Product: Ant
   Version: 1.6Beta
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Minor
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]




Works fine on first pass (i.e. when the link does not already exist), however on
a second pass (i.e. when the link does exist) the result is a link inside the
original directory. That is suppose that:

${project.webapp}/skins/${project.skin} = a/skins/b
${project.home}/${project.skins-dir}/${project.skin} = x/y/b

The first pass gives:

a/skins/b --> x/y/b

but the second pass results in a second link in x/y/b as follows:

b --> x/y/b



A workaround is available for those experienceing this problem:




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant/src/testcases/org/apache/tools/ant BuildFileTest.java

2003-12-03 Thread antoine

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 time stamps on the FAT
 see 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/filetime_str.asp
 for more information
  
  2) prevent XalanLiaisonTest and XslpLiaisonTest from running in batch
 when Xerces1 is not available,
  
  3) fix one of the 3 failing testcases (testSimple) from JDependTest
 it was failing due to an overdose of \r in the output coming from
 BuildFileTest
  
  Revision  ChangesPath
  1.25  +1 -5  ant/src/testcases/org/apache/tools/ant/BuildFileTest.java
  
  Index: BuildFileTest.java
  ===
  RCS file: 
/home/cvs/ant/src/testcases/org/apache/tools/ant/BuildFileTest.java,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- BuildFileTest.java17 Jul 2003 10:39:07 -  1.24
  +++ BuildFileTest.java3 Dec 2003 21:58:08 -   1.25
  @@ -215,11 +215,7 @@
   if (!cr) {
   cleanedBuffer.append(ch);
   } else {
  -if (ch == '\n') {
  -cleanedBuffer.append(ch);
  -} else {
  -cleanedBuffer.append('\r').append(ch);
  -}
  +cleanedBuffer.append(ch);
   }
   }
   return cleanedBuffer.toString();
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant/src/testcases/org/apache/tools/ant/taskdefs JarTest.java

2003-12-03 Thread antoine

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 of time stamps on the FAT
 see 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/filetime_str.asp
 for more information
  
  2) prevent XalanLiaisonTest and XslpLiaisonTest from running in batch
 when Xerces1 is not available,
  
  3) fix one of the 3 failing testcases (testSimple) from JDependTest
 it was failing due to an overdose of \r in the output coming from
 BuildFileTest
  
  Revision  ChangesPath
  1.23  +6 -1  
ant/src/testcases/org/apache/tools/ant/taskdefs/JarTest.java
  
  Index: JarTest.java
  ===
  RCS file: 
/home/cvs/ant/src/testcases/org/apache/tools/ant/taskdefs/JarTest.java,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- JarTest.java  3 Apr 2003 06:06:00 -   1.22
  +++ JarTest.java  3 Dec 2003 21:58:07 -   1.23
  @@ -66,6 +66,7 @@
   import java.util.zip.ZipEntry;
   import java.util.zip.ZipFile;
   import org.apache.tools.ant.BuildFileTest;
  +import org.apache.tools.ant.taskdefs.condition.Os;
   
   /**
* @author Erik Meade <[EMAIL PROTECTED]>
  @@ -160,8 +161,12 @@
   
   private void testRecreate(String firstTarget, String secondTarget) {
   executeTarget(firstTarget);
  +int sleeptime = 2500;
  +if (Os.isFamily("windows")) {
  +sleeptime += 2500;
  +}
   try {
  -Thread.currentThread().sleep(2500);
  +Thread.currentThread().sleep(sleeptime);
   } catch (InterruptedException e) {
   } // end of try-catch
   File jarFile = new File(getProjectDir(), tempJar);
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant build.xml

2003-12-03 Thread antoine

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 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/filetime_str.asp
 for more information
  
  2) prevent XalanLiaisonTest and XslpLiaisonTest from running in batch
 when Xerces1 is not available,
  
  3) fix one of the 3 failing testcases (testSimple) from JDependTest
 it was failing due to an overdose of \r in the output coming from
 BuildFileTest
  
  Revision  ChangesPath
  1.404 +7 -0  ant/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/ant/build.xml,v
  retrieving revision 1.403
  retrieving revision 1.404
  diff -u -r1.403 -r1.404
  --- build.xml 3 Dec 2003 13:16:01 -   1.403
  +++ build.xml 3 Dec 2003 21:58:07 -   1.404
  @@ -556,6 +556,9 @@
   
  +
   
  @@ -1498,6 +1501,10 @@
 
 
  +  
  +

cvs commit: ant build.xml

2003-12-03 Thread antoine

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 of time stamps on the FAT
 see 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/filetime_str.asp
 for more information
  
  2) prevent XalanLiaisonTest and XslpLiaisonTest from running in batch
 when Xerces1 is not available,
  
  3) fix one of the 3 failing testcases (testSimple) from JDependTest
 it was failing due to an overdose of \r in the output coming from
 BuildFileTest
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.392.2.12 +7 -0  ant/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/ant/build.xml,v
  retrieving revision 1.392.2.11
  retrieving revision 1.392.2.12
  diff -u -r1.392.2.11 -r1.392.2.12
  --- build.xml 3 Dec 2003 13:22:29 -   1.392.2.11
  +++ build.xml 3 Dec 2003 22:06:41 -   1.392.2.12
  @@ -555,6 +555,9 @@
   
  +
   
  @@ -1497,6 +1500,10 @@
 
 
  +  
  +

cvs commit: ant/src/testcases/org/apache/tools/ant/taskdefs JarTest.java

2003-12-03 Thread antoine

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
 testRecreateZipfilesetWithUpdateNewerFile,
 the problem is the granularity of time stamps on the FAT
 see 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/filetime_str.asp
 for more information
  
  2) prevent XalanLiaisonTest and XslpLiaisonTest from running in batch
 when Xerces1 is not available,
  
  3) fix one of the 3 failing testcases (testSimple) from JDependTest
 it was failing due to an overdose of \r in the output coming from
 BuildFileTest
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.22.2.1  +6 -1  
ant/src/testcases/org/apache/tools/ant/taskdefs/JarTest.java
  
  Index: JarTest.java
  ===
  RCS file: 
/home/cvs/ant/src/testcases/org/apache/tools/ant/taskdefs/JarTest.java,v
  retrieving revision 1.22
  retrieving revision 1.22.2.1
  diff -u -r1.22 -r1.22.2.1
  --- JarTest.java  3 Apr 2003 06:06:00 -   1.22
  +++ JarTest.java  3 Dec 2003 22:06:41 -   1.22.2.1
  @@ -66,6 +66,7 @@
   import java.util.zip.ZipEntry;
   import java.util.zip.ZipFile;
   import org.apache.tools.ant.BuildFileTest;
  +import org.apache.tools.ant.taskdefs.condition.Os;
   
   /**
* @author Erik Meade <[EMAIL PROTECTED]>
  @@ -160,8 +161,12 @@
   
   private void testRecreate(String firstTarget, String secondTarget) {
   executeTarget(firstTarget);
  +int sleeptime = 2500;
  +if (Os.isFamily("windows")) {
  +sleeptime += 2500;
  +}
   try {
  -Thread.currentThread().sleep(2500);
  +Thread.currentThread().sleep(sleeptime);
   } catch (InterruptedException e) {
   } // end of try-catch
   File jarFile = new File(getProjectDir(), tempJar);
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant/src/testcases/org/apache/tools/ant BuildFileTest.java

2003-12-03 Thread antoine

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
 testRecreateZipfilesetWithUpdateNewerFile,
 the problem is the granularity of time stamps on the FAT
 see 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/filetime_str.asp
 for more information
  
  2) prevent XalanLiaisonTest and XslpLiaisonTest from running in batch
 when Xerces1 is not available,
  
  3) fix one of the 3 failing testcases (testSimple) from JDependTest
 it was failing due to an overdose of \r in the output coming from
 BuildFileTest
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.24.2.1  +1 -5  ant/src/testcases/org/apache/tools/ant/BuildFileTest.java
  
  Index: BuildFileTest.java
  ===
  RCS file: 
/home/cvs/ant/src/testcases/org/apache/tools/ant/BuildFileTest.java,v
  retrieving revision 1.24
  retrieving revision 1.24.2.1
  diff -u -r1.24 -r1.24.2.1
  --- BuildFileTest.java17 Jul 2003 10:39:07 -  1.24
  +++ BuildFileTest.java3 Dec 2003 22:06:41 -   1.24.2.1
  @@ -215,11 +215,7 @@
   if (!cr) {
   cleanedBuffer.append(ch);
   } else {
  -if (ch == '\n') {
  -cleanedBuffer.append(ch);
  -} else {
  -cleanedBuffer.append('\r').append(ch);
  -}
  +cleanedBuffer.append(ch);
   }
   }
   return cleanedBuffer.toString();
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Failing testcases [was Macrodef @{x}]

2003-12-03 Thread Antoine Lévy-Lambert

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 failing, and is currently disabled in
build.xml.

Here is the output of one of the failing testcase of JDependTest :

[junit] Testcase: testXml took 0,08 sec
[junit] FAILED
[junit] expecting output to contain "java.lang"
output was "
[junit] 
[junit] 

[junit] 
[junit] No stats available: package referenced, but
not analyzed.
[junit] 

[junit] 
[junit] No stats available: package referenced, but
not analyzed.
[junit] 

[junit] 
[junit] 
[junit] 2
[junit] 2
[junit] 0
[junit] 0
[junit] 2
[junit] 0
[junit] 1
[junit] 0
[junit] 

[junit] 
[junit] 

[junit] 
[junit]
org.apache.tools.ant.util.facade.FacadeTaskHelperTest
[junit]
org.apache.tools.ant.util.facade.ImplementationSpecificArgumentTest
[junit] 

[junit] 
[junit] junit.framework
[junit] org.apache.tools.ant.types
[junit] 

[junit] 
[junit] 
[junit] 
[junit] 

[junit] 
[junit] 
[junit] 

Cheers,

Antoine

-Ursprüngliche Nachricht-
Von: Peter Reilly [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 3. Dezember 2003 18:15
An: Ant Developers List
Betreff: Re: AW: Macrodef @{x}

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
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

38 matches

Mail list logo