Just as a curiosity, I remember 1 - 1.5 yrs ago when I was somewhat active
on this list, it was a big deal when ant finally decided to drop support
for running ant under java 1.1 and allow use of Collections & other 1.2
stuff in the code base. Did you guys move to 1.4 when I wasn't watching
(th
Steve Loughran wrote:
Peter Reilly wrote:
[EMAIL PROTECTED] wrote:
I had a project where a code generator inserts one interface
statement - and that
what missing. So I created just an empty interface to make the
compiler happy. Couldnt
we "backport" the Iterable interface?
I played a little with
stevel 2005/04/21 06:33:48
Modified:src/main/org/apache/tools/ant AntTypeDefinition.java
Log:
javadocs
Revision ChangesPath
1.17 +1 -1 ant/src/main/org/apache/tools/ant/AntTypeDefinition.java
Index: AntTypeDefinition.java
stevel 2005/04/21 06:33:13
Modified:src/main/org/apache/tools/ant/types AbstractFileSet.java
src/main/org/apache/tools/ant/util
ConcatFileInputStream.java DOMUtils.java
src/main/org/apache/tools/zip UnrecognizedExtraField.java
Log:
Peter Reilly wrote:
[EMAIL PROTECTED] wrote:
I had a project where a code generator inserts one interface statement
- and that
what missing. So I created just an empty interface to make the
compiler happy. Couldnt
we "backport" the Iterable interface?
I played a little with these...
- build.xml
Matt Benson wrote:
Any thoughts on the propriety of adding
public void iterator() {
//return property NAMES
}
to PropertySet? This would make it easy to use with
ant-contrib's task. Not that we have an
obligation to do that, but I think it could be cool.
It would be nice!
Peter
-Matt
_
peterreilly2005/04/21 04:27:08
Modified:src/main/org/apache/tools/ant/taskdefs MacroInstance.java
Log:
just change the exception and not make a new exception
when hiding the macro
Revision ChangesPath
1.35 +2 -1
ant/src/main/org/apache/tools/ant/taskdefs/Macr
Compile under 1.4 and you only have a comment. The oata.Iterable defines the
same
behaviour so external tools could use
- reflection for 1.4 compiled code
- direct access for 1.5 compiled code
Jan
> -Ursprüngliche Nachricht-
> Von: Peter Reilly [mailto:[EMAIL PROTECTED]
> Gesendet am: Do
[EMAIL PROTECTED] wrote:
I had a project where a code generator inserts one interface statement
- and that
what missing. So I created just an empty interface to make the
compiler happy. Couldnt
we "backport" the Iterable interface?
I played a little with these...
- build.xml
- src\oata\Iterable.
Stefan Bodewig wrote:
On Thu, 21 Apr 2005, Peter Reilly <[EMAIL PROTECTED]> wrote:
what I need is
+} else {
+throw ex;
+}
This will cause the error to be reported from within the macro
definition. (i.e. from within the antlib resource).
True, s
On Thu, 21 Apr 2005, Peter Reilly <[EMAIL PROTECTED]> wrote:
> Stefan Bodewig wrote:
>
>>On 21 Apr 2005, <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>> add backtrace attribute to
>>>
>>>
>>
>>hidemacro with reversed meaning (and a default of false)?
>>
>>
> Mmm, I do not know which is more confusing :-
On Thu, 21 Apr 2005, Peter Reilly <[EMAIL PROTECTED]> wrote:
>>what I need is
>>
>> +} else {
>> +throw ex;
>> +}
>>
>>
> This will cause the error to be reported from within the macro
> definition. (i.e. from within the antlib resource).
True, so what I
Stefan Bodewig wrote:
On 21 Apr 2005, <[EMAIL PROTECTED]> wrote:
add backtrace attribute to
hidemacro with reversed meaning (and a default of false)?
Mmm, I do not know which is more confusing :-(
perhaps backtraceonerror (again) ?
Peter
Stefan
-
Stefan Bodewig wrote:
On 21 Apr 2005, <[EMAIL PROTECTED]> wrote:
add backtrace attribute to
On second glance, this is not what I need 8-(
+
+backtrace
+
+ This controls the error traceback if they is an
+ error detected when running the macr
On 21 Apr 2005, <[EMAIL PROTECTED]> wrote:
> add backtrace attribute to
hidemacro with reversed meaning (and a default of false)?
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PRO
On 21 Apr 2005, <[EMAIL PROTECTED]> wrote:
> add backtrace attribute to
On second glance, this is not what I need 8-(
> +
> +backtrace
> +
> + This controls the error traceback if they is an
> + error detected when running the macro. If this i
peterreilly2005/04/21 02:52:05
Modified:docs/manual/CoreTasks macrodef.html
Log:
typeo
Revision ChangesPath
1.26 +1 -1 ant/docs/manual/CoreTasks/macrodef.html
Index: macrodef.html
===
RCS f
peterreilly2005/04/21 02:49:55
Modified:.WHATSNEW
docs/manual/CoreTasks macrodef.html
src/etc/testcases/taskdefs macrodef.xml
src/main/org/apache/tools/ant/taskdefs MacroDef.java
MacroInstance.java
or
public class Something
#ifdef JAVA15
implements Iterable, Closeable
#endif
-and we pump all the source through m5 , velocity, whatever.
just a thought :)
[EMAIL PROTECTED] wrote:
Ok - inlined ...
Jan
build.xml
---8-<---8-<---8-<---8-<---8-<---8-<---8-<---8-<
On this topic, what do people think of the ability to define a filter
set from a property set, where each filter has the property's name and
the property's value?
Phil :n.
On Wed, 2005-04-20 at 16:48 -0500, Dominique Devienne wrote:
> > From: Matt Benson [mailto:[EMAIL PROTECTED]
> >
> > Any tho
On Wed, 20 Apr 2005, Matt Benson <[EMAIL PROTECTED]> wrote:
> We know that the new ResourceCollections stuff will
> add getInputStream() to oata.types.Resource . I think
> the subject of OutputStreams has come up as well, and
> I am starting to think it makes sense to do this,
+1
But we need to
Ok - inlined ...
Jan
build.xml
---8-<---8-<---8-<---8-<---8-<---8-<---8-<---8-<
onJDK15: ${onJDK15}
Using Java 5 stuff
Hiding Java 5 stuff
---8-<---8-<---8-<---8-<---8-<
Title: AW: PropertySet.iterator()
I had a project where a code generator inserts one interface statement - and that
what missing. So I created just an empty interface to make the compiler happy. Couldnt
we "backport" the Iterable interface?
I played a little with these...
- build.xml
- src\o
23 matches
Mail list logo
