Antoine Levy-Lambert wrote:
We should also move the starteam tasks to an antlib or or find another project wanting to have them so that we sometime reach the situation where an automated process (gump ?) could build a release candidate of ant legally on an ASF computer.
Regards,
Antoine
--
Dominique Devienne wrote:
> empty. If foo is empty by mistake, how will one troubleshoot this?
and not a blank line. Undefined properties are echoed as literal
text, not skipped.
I'm well aware of that ;-) That's why I wrote "empty", not "not
defined". As in empty string vs null string.
The
Dominique Devienne wrote:
unless someone comes up with a good reason
why this is a bug rather than a feature.
It's a bug if it doesn't prefix that line with [echo] in non-emacs mode.
is not much different from ${foo} with foo being
empty. If foo is empty by mistake, how will one troubleshoot
Antoine Levy-Lambert wrote:
Hi Steve,
I think you are a committer too. Feel free to edit the documentation.
Regards,
Antoine
Steve Cohen wrote:
A very minor point:
The ant manual states that the echo task's message attribute is
required "unless data is included in a charact
A very minor point:
The ant manual states that the echo task's message attribute is required "unless
data is included in a character section within this element."
This appears to be false. I have by accident discovered that
has the effect of inserting a totally blank line into the output.
+1
Matt Benson wrote:
Sorry I kept forgetting...
Here's my +1.
-Matt
--- [EMAIL PROTECTED] wrote:
I´m just getting the results of the vote. But I´m
not sure which action from the bylaws
to use. An "Adoption of New Codebase" needs 2/3
majority of committers which we havent (~ 1/3).
Many com
Having spent a week thinking over the issues raised in this discussion:
http://issues.apache.org/bugzilla/show_bug.cgi?id=31744
I have come to the conclusion that the best place to start would be creating a
connection as a referenceable object. I'm trying to find a model to look at so
that I
Steve Loughran wrote:
[EMAIL PROTECTED] wrote:
scohen 2005/05/29 17:40:21
Modified:src/testcases/org/apache/tools/ant/taskdefs/optional/net
FTPTest.java
src/main/org/apache/tools/ant/taskdefs/optional/net
FTP.java
src/etc/testc
Stefan Bodewig wrote:
On Mon, 30 May 2005, Steve Cohen <[EMAIL PROTECTED]> wrote:
In log4j, commons-logging, etc. a common pattern is
if (isDebugEnabled()) {
// some expensive string building to put message together
log.debug(expensiveMessage);
}
I don't see such functiona
In log4j, commons-logging, etc. a common pattern is
if (isDebugEnabled()) {
// some expensive string building to put message together
log.debug(expensiveMessage);
}
The point is that without the isXXXEnabled(), the expensive string
building must occur even if the most verbose logger activ
Stephane Bailliez wrote:
Steve Cohen wrote:
However, my knowledge of Ant internals is somewhat limited. How can I
tell an ant project in my test code that when it sees an tag, it
should delegate the performance of this task to myRetryableFTP,
instead of to the standard FTP as it would
Neeme Praks has sent me an interesting patch that allows the task
to execute with a certain number of retries specified. That is, it
won't fail until the specified number of retries has passed.
I want to write some JUnit tests to test this patch. My idea was to
simulate failure by subclassi
Steve Loughran wrote:
Steve Cohen wrote:
what is fetch.xml? Sounds interesting.
I thought you knew; you updated lib/libraries.properties like you did,
that being the property file that drives it.
Actually, I grepped through the source for jakarta-commons and found
libraries.properties
Peter Reilly wrote:
Steve Loughran wrote:
Steve Cohen wrote:
There have been some comments on the jpackage.org mailing list to the
effect that our manual doesn't really have correct installation
instructions for that environment, although elsewhere on our site we
do link to them.
I
Peter Reilly wrote:
Steve Loughran wrote:
Steve Cohen wrote:
There have been some comments on the jpackage.org mailing list to the
effect that our manual doesn't really have correct installation
instructions for that environment, although elsewhere on our site we
do link to them.
I
ver suggestions you
might have on this score or alternative ideas to improve this code.
Steve Cohen wrote:
Antoine Levy-Lambert wrote:
Hello Steve,
what about using a class derived from EnumeratedAttribute as type for
timest
Antoine Levy-Lambert wrote:
Hello Steve,
what about using a class derived from EnumeratedAttribute as type for
timestampGranularity ?
Cheers,
Antoine
[EMAIL PROTECTED] wrote:
scohen 2005/05/22 11:48:42
Modified:src/main/org/apache/tools/ant/taskdefs/optional/net
FTP.java
There have been some comments on the jpackage.org mailing list to the
effect that our manual doesn't really have correct installation
instructions for that environment, although elsewhere on our site we do
link to them.
I have rewritten the install manual page to add this content, but rather
Stefan Bodewig wrote:
Hi,
it's my strong belief that part of the reason the javah and move bugs
made it into 1.6.3 is that our branches are living too long. The same
happened to 1.5.2 (which required 1.5.3 quickly) because the 1.5
branch lived to long (IMHO).
In my day-to-day Ant usage I use C
Antoine Levy-Lambert wrote:
Hello,
I propose to release Ant 1.6.5 on Thursday, June 2nd.
This will be a pure bug fix release.
[] Yes
[] No
Let's begin with my +1
Cheers,
Antoine
-
To unsubscribe, e-mail: [EMAIL PROTECTE
Stefan Bodewig wrote:
On Mon, 23 May 2005, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote:
we should add a line about in in the table explainning the different
system properties used by Ant.
Keep in mind that it is our wrapper script that sets the property. If
you launch ant any other way
Alexey Solofnenko wrote:
Please use ${ant.home} property.
- Alexey.
On 5/22/05, Steve Cohen <[EMAIL PROTECTED]> wrote:
I am trying to write a simple build.xml for debugging Ant setups. One
of the things I would like to know is what ANT_HOME was defined as when
Ant launched. But this do
I am trying to write a simple build.xml for debugging Ant setups. One
of the things I would like to know is what ANT_HOME was defined as when
Ant launched. But this does not seem to be a predefined ant property.
I naively thought that I could do
ANT_HOME=${env.ANT_HOME}
this will not
Nachricht ---
Von: Steve Cohen <[EMAIL PROTECTED]>
An: Ant Developers List
Betreff: Release Notes Link Broken
Datum: Sat, 21 May 2005 06:15:06 -0500
The "release notes" link on http://ant.apache.org/srcdownload.cgi, which
points to http://mirrons.combose.com/apache/ant/README.htm
The "release notes" link on http://ant.apache.org/srcdownload.cgi, which
points to http://mirrons.combose.com/apache/ant/README.html is broken.
I get a 403 Forbidden error. Is this where the link should point?
-
To unsubscrib
an
-Ursprüngliche Nachricht-
Von: Alexey N. Solofnenko [mailto:[EMAIL PROTECTED]
Gesendet am: Mittwoch, 18. Mai 2005 06:05
An: Ant Developers List
Betreff: Re: cvs commit: ant/docs/manual/OptionalTasks ftp.html
Actually, > is also not required.
- Alexey.
Steve Cohen wrote:
To be hon
Peter Reilly wrote:
Martin Gainty wrote:
Not to mention > and other escaped characters
No,
Dominique was correctly compaining about the needless escaping of the
quote characters
Peter
Can the Ant mail server either parse the html escaped characters and
insert the correct character representation
Antoine Levy-Lambert wrote:
Do not worry if you are sure that the current behavior is buggy.
Cheers,
Antoine
Well, I went and logged a bug on the issue thinking that this might
provoke a little more discussion. Unfortunately, bugzilla seems to not
have sent out an email about it, so it will get
Martijn Kruithof wrote:
Steve Cohen wrote:
In trying to bring over new commons-net timezone functionaility, I
discover the following:
protected boolean isUpToDate(FTPClient ftp, File localFile,
String remoteFile)
throws IOException, BuildException
In trying to bring over new commons-net timezone functionaility, I
discover the following:
protected boolean isUpToDate(FTPClient ftp, File localFile,
String remoteFile)
throws IOException, BuildException {
...
if (this.action == SEND_FILES) {
Steve Cohen wrote:
Shall the newly added FTP task revisions be incorporated into release
1.6.4?
I'm withdrawing this vote request.
Although commons-net functions as expected, the relationship with the
FTP task is a little more complicated than I'd thought, and those who
have expre
Steve Loughran wrote:
Steve Cohen wrote:
Shall the newly added FTP task revisions be incorporated into release
1.6.4?
Motivation:
I understand this comes in "under the wire" and may cause justifiable
trepidation among some. I still favor adding it to the release because:
1) The task
ools/ant/taskdefs/optional/net/FTPConfigurator.java (new) 1.2
/ant/docs/manual/OptionalTasks/FTP.html 1.32
/ant/docs/manual/install.html 1.83
/ant/lib/libraries.properties 1.3
Steve Cohen
-
To unsubscribe, e-mail: [EMAIL PROTECT
ools/ant/taskdefs/optional/net/FTPConfigurator.java (new) 1.2
/ant/docs/manual/OptionalTasks/FTP.html 1.32
/ant/docs/manual/install.html 1.83
/ant/lib/libraries.properties 1.3
Steve Cohen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Stefan Bodewig wrote:
On Thu, 12 May 2005, Steve Cohen <[EMAIL PROTECTED]> wrote:
I don't know, though, guys. What do you think? Is it really worth
it to avoid making the users upgrade?
For me it depends on when you wanted to see the new task.
If you wanted to include it in 1.6.
Steve Cohen wrote:
Steve Cohen wrote:
Stefan Bodewig wrote:
On 12 May 2005, <[EMAIL PROTECTED]> wrote:
+For all users, a minimum version of commons-net of 1.4.0 is
now required.
Is this really true?
I understand it is required to compile or if you use one of
the new features. But
Steve Cohen wrote:
Stefan Bodewig wrote:
On 12 May 2005, <[EMAIL PROTECTED]> wrote:
+For all users, a minimum version of commons-net of 1.4.0 is now
required.
Is this really true?
I understand it is required to compile or if you use one of
the new features. But if you use the sa
Stefan Bodewig wrote:
On 12 May 2005, <[EMAIL PROTECTED]> wrote:
+For all users, a minimum version of commons-net of 1.4.0 is now required.
Is this really true?
I understand it is required to compile or if you use one of
the new features. But if you use the same way you did
before and use
nformation by unintended recipients is prohibited. Any opinions
expressed in this e-mail are those of the author personally.
Steve Cohen <[EMAIL PROTECTED]> wrote on 12/05/2005 08:38:39 PM:
Antoine Levy-Lambert wrote:
Steve Cohen wrote:
However, it does seem to me that this test case is r
Jose Alberto Fernandez wrote:
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Nicola Ken Barozzi
Stefan Bodewig wrote:
On Wed, 11 May 2005, Jose Alberto Fernandez
<[EMAIL PROTECTED]> wrote:
I do not think we can continue maintaining tasks for every
project in
the world just because they do
Stefan Bodewig wrote:
On Wed, 11 May 2005, Steve Cohen <[EMAIL PROTECTED]> wrote:
I recently spent some time looking over jpackage.org. Have you guys
seen this operation?
More than that. We modified the Ant wrapper script to suit their
needs, so that they could stop distributing their v
Stefan Bodewig wrote:
On Wed, 11 May 2005, Steve Cohen <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
If the tests pass - why not? :-)
I wanted to discuss "the tests" and what is meant by that.
When I saw Jan's remark I thought he must have been joking. I
wouldn'
Antoine Levy-Lambert wrote:
Steve Cohen wrote:
However, it does seem to me that this test case is rather incomplete,
and could be beefed up in several ways to test these and other recent
features of commons-net which are not being tested here.
Feel free to expand this test. I created this test
the author of the
commons-net code that Mr. Praks is relying on, and an Ant
committer, I
would be happy to take a look at his code and "sponsor" it
for the 1.6.4
release.
I realize that there may be other deadlines here. What do other Ant
committers think?
Steve Cohen
If the
Stefan Bodewig wrote:
On Wed, 11 May 2005, Steve Cohen <[EMAIL PROTECTED]> wrote:
Other parts of Mr. Praks' patch are less simple (retry handler,
etc.) and I've asked him to remove those for now. These definitely
belong in CVS_HEAD after the release.
The release comes from a br
Stefan Bodewig wrote:
On Wed, 11 May 2005, Jose Alberto Fernandez
<[EMAIL PROTECTED]> wrote:
I do not think we can continue maintaining tasks for every project
in the world just because they do not want to depend on ANT.
Calm down. We are talking about an existing Ant task that gets used a
lot.
Neeme Praks wrote:
Steve Loughran wrote:
I worry about releasing any change to code without giving it time to
stabilise and beta test. Last minute "this won't break anything"
patches always break something. Always. At least in my experience.
If commons1.4.0 is incompatible with shipping then ye
Stefan Bodewig wrote:
On Tue, 10 May 2005, Steve Cohen <[EMAIL PROTECTED]> wrote:
As the author of the commons-net code that Mr. Praks is relying on,
and an Ant committer, I would be happy to take a look at his code
and "sponsor" it for the 1.6.4 release.
There is no need to sp
o that release? As the author of the
commons-net code that Mr. Praks is relying on, and an Ant committer, I
would be happy to take a look at his code and "sponsor" it for the 1.6.4
release.
I realize that there may be other deadlines here. What do other Ant
committers thi
Steve Loughran wrote:
Jose Alberto Fernandez wrote:
From: Steve Cohen [mailto:[EMAIL PROTECTED]
Jose Alberto Fernandez wrote:
Why not move the task or its new version into jakerta-commons and
provide us with a ready to go feature full antlib. That
would allow us
to start decoupling
things
Jose Alberto Fernandez wrote:
Why not move the task or its new version into jakerta-commons and
provide us with
a ready to go feature full antlib. That would allow us to start
decoupling
things from the main ANT release.
Jose Alberto
I have not been as active in Ant circles as in the past. Is dec
Stefan Bodewig wrote:
On Tue, 10 May 2005, Steve Cohen <[EMAIL PROTECTED]> wrote:
In the next few weeks (months) I am intending to rework the
task to take advantage of these new capabilities.
Maybe Neeme Praks' patch[1] would provide a nice starting point?
Stefan
Footnotes:
The new release of jakarta-commons-1.4.0 contains some features that
were specifically designed with Ant in mind. In particular the
FTPClientConfig class was designed with the thought of enabling the
enhancement of the ant task to
1. handle ftp servers with file listing formats that format da
+ 1
On Tuesday 29 June 2004 8:43 pm, Magesh Umasankar wrote:
> From: Stefan Bodewig
> Date: 2004-06-29 10:00:28
>
> > * Release Candidate on Friday July 2
> >
> > * If nothing major happens, Final Release on July 16.
>
> +1
>
> Cheers,
> Magesh
>
> -
2004 1:50 am, Conor MacNeill wrote:
> Steve,
>
> I did you a welcome to Ant email on 18-Jun to this email address.
> Anyway, whatever, the vote passed and we are glad to have you aboard as
> a committer.
>
> Conor
>
> Steve Cohen wrote:
> > Stefan -
>
6:33 am, Stefan Bodewig wrote:
> On Mon, 28 Jun 2004, Steve Cohen <[EMAIL PROTECTED]> wrote:
> > I'd do it myself,
>
> please do.
>
> > but I'm wondering what is the status of the committer vote that was
> > taken on me a couple of weeks ago.
>
>
FTP task was broken in some cases by changes in commons-net. These were fixed
in the recent release 1.2.2 of commons-net. All that needs to happen in ant
now is for the docs to be updated to mandate use of commons-net 1.2.2.
I'd do it myself, but I'm wondering what is the status of the committ
The Jakarta Commons team announces the release of version 1.2.2 of the
Jakarta Commons/Net component. This release fixes a problem introduced with
recently released version 1.2.0 in which file listings would not correctly
'remember' the current directory when no directory was specified. This ha
pm
From: Steve Cohen <[EMAIL PROTECTED]>
To: announcements@jakarta.apache.org, commons-dev@jakarta.apache.org,
commons-user@jakarta.apache.org
The Jakarta Commons team announces the release of version 1.2.1 of the
Jakarta Commons/Net component. This release fixes recently released
version
This will be a fix release to fix the problem introduced in 1.2.0 that it will
not compile using jdk < 1.4 and nothing else.
Details at http://issues.apache.org/bugzilla/show_bug.cgi?id=28775, which I've
already fixed (and verified against jdk 1.2).
Also, per the advice of Stephen Colburne, thi
in Ant's FTP task, for example, for these
server types as well as the original unix.
Steve Cohen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- End
use in Ant's FTP task, for example, for these
server types as well as the original unix.
Steve Cohen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- End Me
away.
On Tuesday 23 March 2004 3:28 pm, Antoine Lévy-Lambert wrote:
> Hi Joe,
>
> I suggest you create a bugzilla report (
> http://issues.apache.org/bugzilla) concerning this, and you attach your
> patch there.
> I am not sure however whether this problem should best be handled in the
Thanks, got it. Duh. Properties are immutable. I wasn't thinking.
On Thursday 26 February 2004 7:15 am, Stefan Bodewig wrote:
> On Thu, 26 Feb 2004, Steve Cohen <[EMAIL PROTECTED]> wrote:
> > How do you negate a non-boolean property? How do you negate null?
>
> I
On Thursday 26 February 2004 4:12 am, Stefan Bodewig wrote:
> On Fri, 20 Feb 2004, Matt Benson <[EMAIL PROTECTED]> wrote:
> > I have put together a patch for negating the selected
> > properties of a PropertySet.
>
> Sounds useful.
>
> Stefan
>
>
?
On Wednesday 18 February 2004 1:05 am, Daniel F. Savarese wrote:
> In message <[EMAIL PROTECTED]>, Steve Cohen writes:
> >You've built an interface to encapsulate the choice in regex
> > implementations with automatic checking. Sweet! Perhaps we could port
> &
On Tuesday 17 February 2004 8:27 pm, Steve Cohen wrote:
> On Tuesday 17 February 2004 10:11 am, Dominique Devienne wrote:
> > > From: Steve Cohen [mailto:[EMAIL PROTECTED]
> > >
> > > While it is true that the CVS HEAD of commons-net is required and while
> > &g
On Tuesday 17 February 2004 10:11 am, Dominique Devienne wrote:
> > From: Steve Cohen [mailto:[EMAIL PROTECTED]
> >
> > While it is true that the CVS HEAD of commons-net is required and while
> > it is
> > true that jakarta-oro is required (jakarta-oro is now requir
Can someone please clarify the optional jar requirement for ant >= 1.6? The
manual says in one place that you must build ant with the library
dependencies present, and in another place (Installing ant-Optional Tasks) it
states that you can simply drop the dependency jar into ant's lib directory
I see that someone has tried to incorporate my suggestion for using the latest
commons-net.jar in order to use ant's task with NT-based servers.
However, the documentation is not quite correct. It says:
"To use the FTP task with Microsoft FTP servers, you need CVS HEAD of
commons-net and jak
riday 16 January 2004 10:28 am, Peter Reilly wrote:
> Steve Cohen wrote:
> >On Friday 16 January 2004 4:56 am, Steve Loughran wrote:
> >>Steve Cohen wrote:
> >>>Another issue to consider. I don't know if it's strictly a 1.6.1 issue
> >>>or furth
Please ignore. This last comment by me was added in a reply to the wrong
message.
On Friday 16 January 2004 11:18 am, Steve Cohen wrote:
> Well, we at commons-net would have been rushing the release to meet ant's
> "deadline" and there are internal refactorings which w
Well, we at commons-net would have been rushing the release to meet ant's
"deadline" and there are internal refactorings which we would have liked to
have included that we were planning to postpone in the rush, but now will
take the time to get right, so I doubt that commons-net-1.2.0 will be do
On Friday 16 January 2004 4:56 am, Steve Loughran wrote:
> Steve Cohen wrote:
> > Another issue to consider. I don't know if it's strictly a 1.6.1 issue
> > or further down the line but the ant developers should consider it.
> >
> > I have been working wi
ess than a week.
It seems from this thread that these changes will come too late for ant 1.6.1.
Please correct me if that's wrong. Can someone tell me what plans, if any,
are contemplated for ant 1.6.2?
Steve Cohen
On Thursday 15 January 2004 9:50 am, Antoine Lévy-Lambert wrote:
> Hi,
At first I thought you were making a joke, but I now see that these are
serious people. More info on this language can be found at
http://wiki.codehaus.org/groovy/FrontPage
-Original Message-
From: Peter Reilly [mailto:[EMAIL PROTECTED]
Sent: Friday, December 12, 2003 9:54 AM
To: Ant Dev
I have no vote, but if I did it would be +1. I was surprised to learn, a few
weeks ago, that Jose was not a committer.
-Original Message-
From: Antoine Lévy-Lambert [mailto:[EMAIL PROTECTED]
Sent: Friday, December 12, 2003 4:09 AM
To: Ant Developers List
Subject: [VOTE] Jose Alberto Fe
Interesting that in the past week I have heard this complaint three times,
(Bwhereas before I never heard it.
(B
(BSince I did a lot of the most recent work on the commons-net ftp parser stuff,
(Band since I will be having some time on my hands with an upcoming layoff, I
(Bwould like to tak
prungliche Nachricht-----
Von: Steve Cohen [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 9. Dezember 2003 16:14
An: Ant Developers List
Betreff: RE: bug fixes!! WAS: ant 1.6beta3 released
There are improvements to commons-net over the old NetComponents to
handle Windows FTP servers. However, the ant ta
There are improvements to commons-net over the old NetComponents to
handle Windows FTP servers. However, the ant tasks would need to be
recoded to take advantage of these.
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2003 1:48 AM
To: [EMAI
test
Thanks, Jacob, for continuing to pursue this, and deepening my awareness of the
problem.
I appreciate your dilemma, even though I still agree with what has become
consensus that textual substitution is right for . The whole
business with the scope of properties is already complicated enough.
Peter -
>>but if macrodef properties are to be implemented as textual substitution
>>and not as local properties, the two issues can be separated.
Did you mean to say "but if macrodef ATTRIBUTES are to be implemented as
textual substitution and not as local properties ..."
Or are you talking ab
Not a committer but my votes on Jose's ballots:
1) Vote on @{x} as the syntax for textual substitutions
of attributes in .
+1
2) Vote on , must include decision on syntax,
scope (i.e., passing things on & co., etc.)
I do not think all these have been settle.
0
-Original Message-
From:
True, that was from the 1.4/1.5 days.
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 8:52 AM
To: 'Ant Developers List'
Subject: RE: macrodef - do attributes as properties or substitutions
> From: Steve Cohen [
What about {$x}? Or is it too close to a typo for a regular property?
way too confusing, IMHO. And departs significant from our "pattern"
which seems to be
identifier type marker, open curly brace, identifier, close curly brace
The more I look at this, the clearer my clear choice becomes for @{
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 2:06 AM
To: [EMAIL PROTECTED]
Subject: RE: macrodef - do attributes as properties or substitutions
> >
> >
> >
> >
> >
>
> I don't think we should need any special cludge
Another non committer here.
I don't like $(x) because it looks too much like ${x}, although I
suppose I could get used to that. Therfore, I am drawn to
@{x}. ${attribute:x} is possible but way too much typing for my taste.
Abbreviated to ${att:x} or ${attrib:x} my negativity level goes down
accor
>> "I want macrodef for when all I need to do is to put toguether
a group of calls to other tasks in a sequence, which could be
quite complex, but it does not require any additional computation
from my part"
Hear, hear!
Used in this way, you can use ant, cutting out expensive calls and
most 's
Wouldn't you say, though, Jose, that does replace those uses
of for which had too big a footprint for the job?
-Original Message-
From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 11:19 AM
To: Ant Developers List
Subject: RE: macrodef - do attrib
I don't have a vote but if I did, I'd be
[X] as textual substitution
[ ] as "real" Ant properties
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 10:14 AM
To: 'Ant Developers List'
Subject: RE: [VOTE] macrodef - do attributes as pr
her. If we are going to introduce macros in ant, I think that the
clarity of knowing that they are defined at load time, and not at
runtime is an advantage.
has never been a good way to do "templates".
Although I might be open to a convincing counter-example.
Steve Cohen
Sr. Software
erent sorts of beasts and this should not be muddied.
Steve Cohen
Sr. Software Engineer
Sportvision, Inc.
scohenATSportvisionDOTcom
-Original Message-
From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2003 10:30 AM
To: Ant Developers List
Subject: RE: attri
ED]
Subject: Re: MARC - spam enabler
On Fri, 31 Oct 2003, Steve Cohen wrote:
> Can't MARC be fixed to munge email addresses?
Even if it could, it wouldn't help you.
> but whenever I am replied to, my full unmunged email address gets
> published in MARC.
I've j
back at myself. I just got rid of one email address, and soon
I'll be forced to do so again. Can nothing be done about this?
Steve Cohen
Sr. Software Engineer
Sportvision, Inc.
scohenATSportvisionDOTcom
ntoine's question is whether the new
notation would have to be scrapped for the new implementation of local
in 1.7 or whether it would still apply.
Unless this is going to delay the release for months, I would say, get
it right, now.
Steve Cohen
Sr. Software Engineer
Sportvision, Inc.
scohenATSpor
: Tale from the front: macrodef nesting
> From: Steve Cohen [mailto:[EMAIL PROTECTED]
>
> You're correct about working around this problem. However, I think
> it's still a problem that the same ${identifier} notation can either
> indicate a macrodef attribute or an a
to Fernandez [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 5:37 AM
To: Ant Developers List
Subject: RE: Tale from the front: macrodef nesting
> From: Steve Cohen [mailto:[EMAIL PROTECTED]
>
> I am now trying to experiment with some of the new features
> of ant 1.6. He
: Ant Developers List
Cc:
Subject:Re: Question about MacroDef vs antcall
On Sun, 26 Oct 2003 03:18 am, Steve Cohen wrote:
> The new ant features wiki
>
> http://nagoya.apache.org/wiki/apachewiki.cgi?NewAntFeaturesInDetail/MacroDe
>f
>
> says:
>
> "
I am now trying to experiment with some of the new features of ant 1.6. Here's
a real-world example of the difficulties of trying to replace antcalls with
macrodefs.
Given the following definitions, notice that I am trying to nest a call to the
macrodef make.precompiled.web.xml inside a call to
1 - 100 of 141 matches
Mail list logo
