I get a 404 when trying to download the 1.5.2 ZIP from the Ant main page.
--DD
-Original Message-
From: Magesh Umasankar [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2003 9:37 AM
To: Ant Developers List; user@ant.apache.org
Cc: announcements@xml.apache.org; [EMAIL PROTECTED];
announ
Changed the mirror to something else than InetCosmos, and it worked (the
former was the default selected though). --DD
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2003 9:42 AM
To: 'Ant Developers List'
Subject: RE: [ANN]
Not directly related, but I recently read that Maven similarly moved away
from relative path to use absolute paths. They apparently prefix ${basedir}
explicitly everywhere. I'm not following the dev forum, but thought the
parallel was worth mentioning. --DD
-Original Message-
From: Steve L
This is indeed interesting. I do something quite similar for another purpose
(scans a JAR for all classes having a give static method signature, executes
all these methods, gathering the meta-info required, generate a XML file
then stuck into the JAR's META-INF directory).
Something I do is to res
But where does it stop? also supports automatic ordering of the
projects called based on the declared dependencies of the projects in an XML
file... Should that go into as well? (granted, I didn't submit that,
it's only in my sandbox...)
According to your reasoning, features should have gone in
ED]
Subject: Re: Possible TaskDef donation
Dominique Devienne wrote:
> This is indeed interesting. I do something quite similar for another
purpose
> (scans a JAR for all classes having a give static method signature,
executes
> all these methods, gathering the meta-info required, generate
+1
-Original Message-
From: Conor MacNeill [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 5:29 PM
To: [EMAIL PROTECTED]
Subject: JDK 1.1 support
I'd like to throw this up again. What are peoples thoughts on the following
1. Make Ant 1.6.x the last JDK 1.1 release. This would b
I actually signed off , not , technically, but in practice I
give both. Anything I submit to BugZilla is good for the taking, and I'll
refrain to include my usual/automatic copyright notice in the future.
Sorry to hear you suppressed passing down the current target name... That
one of the feature
ferred instead of being statically defined.
*
* Provides the famous extra level of indirection which is the
* solution to all computing problems ;-)
*
* @author mailto:[EMAIL PROTECTED]">Dominique Devienne
* @version Nov 2002 - Copyright (c) 2002, Landmark Graphics Corp.
*
* @see Buil
9:51 AM
To: Ant Developers List
Cc: [EMAIL PROTECTED]
Subject: Re: subant
Dominique Devienne wrote, On 14/03/2003 16.23:
> The dependency ordering addition is pluggeable... you just provide a
> resolver implementation.
Wow! :-D
Excellent news, very nice!
...
> I already submitted SubAnt.java
ime IMHO.
--DD
PS: I'll post the new with within a few weeks.
-Original Message-
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2003 10:16 AM
To: Ant Developers List
Cc: [EMAIL PROTECTED]
Subject: Re: subant
Dominique Devienne wrote, On 14/03/2003
I'm trying to achieve a slightly different goal, specific to our needs here
;-) I'll try to get subant/buildpath out quickly with a proper license,
disclaimer, and an example impl that could be used by anyone.
Cheers, --DD
-Original Message-
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECT
+1
-Original Message-
From: Conor MacNeill [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2003 12:45 AM
To: [EMAIL PROTECTED]
Subject: [VOTE] JDK 1.1 support
Hi,
This is to formalize the discussions which have gone on on the dev and user
lists. Please indicate your vote. Everyone
I'm not following this line of thought...
) remove spurious debug output
2) add alltargetspath
3) make all attributes optional (so there is no need
for property="notused"
Peter
On Friday 21 March 2003 23:11, Dominique Devienne wrote:
> I'm not sure you understood me correctly...
>
> I want to force the regenera
Look at the filter chain available in . --DD
-Original Message-
From: Mariya Makarovskaya [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2003 1:19 PM
To: '[EMAIL PROTECTED]'
Subject: filtersfile
Hello,
is it possible to have filtersfile to map tokens to properties. And how
should I
Yes ;-) Me, and other people too. There is in Ant's BugZilla one task called
that was recently added to the HEAD (slightly modified) on an
experimental basis, and there's also a patch to along the same lines.
There has been quite a bit of discussion about both (one vs. the other even)
on ant-dev
t: Tuesday, March 25, 2003 4:07 PM
To: Ant Developers List
Subject: Re: Ant task and dirset/fileset
Ok I searched bugzilla and subant appears exactly once... but it says it
is committed. Problem is I don't see it in the manual, where can I get
some doc for it? (or do I need to go find th
Could someone please explain me what SuiteRunner brings to the table that
JUnit doesn't I've looked at it quite a bit, and maybe beside better
reporting, I don't see anything compelling about it compared to JUnit, and
even loose the built-in assert methods of TestCase (thru Assert)...
I'd be i
Leigh Ishikawa. Any
advice on that matter?
Thanks,
Adam
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: 26 March 2003 15:20
To: 'Ant Developers List'
Subject: RE: Artima SuiteRunner Task
Could someone please explain me what SuiteRunner brings to the t
tima.com to see if their
interested. :)
Thanks again,
Adam
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: 26 March 2003 15:37
To: 'Ant Developers List'
Subject: RE: Artima SuiteRunner Task
Sorry, I didn't mean at all to put down your contribut
f the
compelling feature is going to be a moving target :)
Also in your example buildfile, I am not sure I understand how the
targets work. It looks like clean, build reversion and rebuild all do
the same thing?
-Gus
Dominique Devienne wrote:
> No doc, no test :-(
>
> Subant accept a , whic
6 Mar 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> That said (one more ;-), if Ant ever comes up with an easier way to
> integrate third party tasks
Easier than ?
Almost impossible.
Stefan
I meant ANT_HOME/lib. --DD
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2003 10:37 AM
To: 'Ant Developers List'
Subject: RE: Artima SuiteRunner Task
Hu, not totally. If the AntLib also uses types, you need another
, wh
I don't buy that. If your exception doesn't contain enough info, then modify
the exception. I never trap exception in Unit tests, unless I'm expecting it
to be thrown and fail() if it doesn't.
As far as running one of more tests, I use a
-Dtestcase=com/acme/SomeTest.class, and testcases defaultsto
tasks registered with Ant
* using either a taskdef or typedef.
*
* @author mailto:[EMAIL PROTECTED]">Dominique Devienne
* @version Mar 2003 - Copyright (c) 2002, Landmark Graphics Corp.
*/
public class DynamicTag
extends Task
implements DynamicConfigurator {
Probably because Stefan is (with you!) the most active committer on Ant ;-)
Thank you both for your fantastic work. --DD
-Original Message-
From: Conor MacNeill [mailto:[EMAIL PROTECTED]
Sent: Friday, April 04, 2003 8:51 AM
To: [EMAIL PROTECTED]
Subject: [RESULT] Ant 1.6 will require JDK
OK, me too I wish Ant was using more URLs instead of files... Using my
little resource: custom URL protocol, I could then easily reference any
resource in $ANT_HOME/lib. Right now though, you can turn around the current
limitations but first doing a of the URL you want (and with resource:
URLs, yo
I've solved that problem for my own purposes a few months ago, by just
hacking a bit at java.c, so it can read it's command line arguments from a
file, using the usual @file syntax (that Javac already supports, but
implemented in Java). Even enabled env. var. substitutions a la Ant, using
the ${env
Did I mention that I use Ant and CppTasks to compile it ;-) --DD
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Monday, April 07, 2003 9:18 AM
To: 'Ant Developers List'; '[
FYI, Javac is not really using java.class.path, but env.class.path
instead... By default, the former will be copied in the later by javac.c.
Discovered this early 2001 when I wrote a little Java front-end to Javac to
be Visual Studio friendly. Could be of use to the discussion??? --DD
-Origina
Stefan is *of course* right! Class.forName always uses the system class
loader, and not some current loader... As far as delegation happening,
that's ClassLoader 101. Unless of course one uses the second form of
Class.forName, that takes a classloader as argument, provided one doesn't
pass null for
I stand corrected, and apologize. --DD
-Original Message-
From: Andrew Haley [mailto:[EMAIL PROTECTED]
Sent: Monday, April 07, 2003 11:53 AM
To: Ant Developers List
Subject: RE: [Patch] trying solve w2k command line length limitations
Dominique Devienne writes:
> Stefan is *of cou
I'm +1 for not overloading .
I also like Stefan's syntax the best from the different proposals, I'd just
drop the set prefix to have simply:
http://www.apache.org/"/>
Note the change to resource (from resources) to be consistent with
/ . I assume the url attribute's signature would be
se
See http://marc.theaimsgroup.com/?l=ant-dev&m=104870800508326&w=2
And http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17199
I prefer the first link, since I'm the author of it, but the second link
addresses the same issue. If your elements do not need any
configurations though, it may be overk
Two comments:
1) DynamicTag is fully Ant 1.5.x compatible. No need for 1.6. Just use it
along side your own classes, and you're good to go.
2) DynamicTag *relies* on or (you can declare your
custom extension either way), which takes care of all the classloading,
already has all the special stuf
I'll try to answer for Stefan, since he won't read your message until
tomorrow because of his timezone...
Yes, 'make ContainsRegexpSelector under /ant/types/selectors ...'. I believe
Stefan was merely pointing out that there are separate classes for filtering
on string literals and regular express
Could you please expand Stefan? What's going on around the idea of
Polymorphism in Ant? (beyond that is)
I vaguely recall the Ant2 proposals had something like Polymorphism, but
they're both long dead, and I can't recall anything concrete around it for
the 1.x Ant line. Thanks for any precisions.
sage-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2003 9:36 AM
To: [EMAIL PROTECTED]
Subject: Re: [Patch] es to be submitted
On Fri, 11 Apr 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> What's going on around the idea of Polymorphism in Ant
lFilter filter) {
filters.addElement(filter);
}
public Vector getFilters() { return filters;}
}
and in XmlChain:
public void addCustomFilters(CustomFilters customFilters) {
this.customFilters = customFilters;
}
Cheers,
Peter
Dominique Devienne wrote:
>>Two comments:
>>1
Why is Ant 1.5.3 shipping with junit.jar in ANT_HOME/lib???
I don't see anything about it in WHATSNEW, nor a LICENSE.junit for that
matter.
Plus the Manifest of that JAR doesn't even say which version of JUnit it is,
just that it was build using Ant 1.4.1 ;-)
Thanks, --DD
-0. Never had to use it in my own builds, so consider it non-essential...
Just kidding ;-) Why not? --DD
-Original Message-
From: Antoine Levy-Lambert [mailto:[EMAIL PROTECTED]
Sent: Monday, April 21, 2003 4:24 AM
To: Ant Developers List
Subject: Re: [VOTE]
+1
Antoine
- Original Me
I agree with Stefan. I much prefer to have AntLib *specified*, as in a
specification of the contract an AntLib must fullfil to be usable but Ant,
than working on the tools themselves to package an AntLib (XDoclet or
whatever else), or even an auto-download feature (I've looked at Ruper, and
I'm not
Works just fine for the purpose of doing s... We don't require anything
fancy here. Getting files thru HTTP with timestamp works for me, and has
been for a while. I've even done simple stuff like extracting properties
from the HTTP header at the same time I'm getting a file (properties added
by a c
One comment about roles: Roles are fine, but roles are just strings... If
everything is defined as a component at a low level, then they can be easily
introspected to find out what interfaces components implement. For example,
why would I have to say:
when class a.b.C does implement FileSelector
ond that, all
other roles are interfaces. What's wrong with that? --DD
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 23, 2003 10:35 AM
To: [EMAIL PROTECTED]
Subject: Re: antlib
On Wed, 23 Apr 2003, Dominique Devienne <[EMAIL PROTECTED]> w
:12 AM
To: [EMAIL PROTECTED]
Subject: Re: antlib
On Wed, 23 Apr 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> Forcing roles to map to an interface is probably a *good* idea!
Maybe, hmm, probably, not convinced ...
> Every single bean would become implicitly a data-type, and t
Yes, it could be a problem. But running the risk of speaking yet another
anathema, I'm starting to believe the Jelly approach of using XML namespaces
is the right one...
The problem is not so much that one wants to use the same name (say
containsregex) for two different things (a condition and a f
Thanks Jose Alberto for the clear use-case of using the AntLib. I do like it
a lot more now that I understand it better ;-)
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 24, 2003 7:04 AM
>
> * antlib needs a way to define mappings between names and classes.
>
> Costin p
> From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 24, 2003 11:39 AM
> > J2SDK1.2 + defines a mechanism for declaring dependencies. Which is
> > actually required for servlet containers and j2ee. (i.e. the
> > manifest ).
> >
> > Why would we want to invent our own ?
> From: Costin Manolache [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 24, 2003 12:23 PM
>
> The common use case is defining tasks and datatypes.
So you -1 roles because you don't need them, at the expense of all the
people who need to declare more than tasks and datatypes, but conditions,
fil
> -Original Message-
> From: Erik Hatcher [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 24, 2003 1:45 PM
>
> But the current one does not support adding other components like
> conditions, mappers, filters, and selectors.
Exactly! Which is why I don't understand Costin's -1. If it wasn
> -Original Message-
> From: Costin Manolache [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 24, 2003 1:57 PM
>
> >> The common use case is defining tasks and datatypes.
> >
> > So you -1 roles because you don't need them, at the expense of all the
> > people who need to declare more tha
> -Original Message-
> From: Costin Manolache [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 24, 2003 2:47 PM
>
> >>> But the current one does not support adding other components like
> >>> conditions, mappers, filters, and selectors.
> >>
> >> Does ant support this ?
> >
> > No, not cur
No need for parsing! Don't know about ClassLoader#getResources??? --DD
> -Original Message-
> From: Costin Manolache [mailto:[EMAIL PROTECTED]
>
> I don't like passing the .jar very much - but that's probably the only
> way if we want to use META-INF/antlib.xml.
>
> The alternative would
My own implementation used Matcher.matches, so you would have to add a
trailing .* to really match all properties not starting with java I think.
Had I used Matcher.find, then it would have been OK. I'm not sure how the
Ant encapsulation of Regexp does it. --DD
> -Original Message-
> From:
This is incorrect, at least with my version. It will attempt to find a
build.xml in all the directories, and FAIL if one cannot be found. To
achieve what you describe, use a fileset:
I understand you had failonerror="true", but then a build failure in any of
the build actually found wo
And a new selector hopefully... I'd like to select JUnit test cases with
more than just a filename pattern. It's actually on my to-do list, and I
should have it within a few weeks (when I get around to it). We've been
doing it for months with a special Unit test which does it in its suite()
method,
age-
> From: Antoine Levy-Lambert [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 14, 2003 10:06 AM
> To: Ant Developers List
> Subject: Re: cvs commit: ant/docs/manual/CoreTasks subant.html
>
> fixed in CVS
> Thanks for the feedback.
> Antoine
> - Original Message ---
The fact that the meaning of was overloaded in the past doesn't
mean we should continue doing so... And still, available currently looks for
files/streams (on file-system, classpath, path, etc...), which is quite
different than looking for particular characteristic of whatever's described
in these
Centipede as a task I think, and I also created one myself a long time
ago... Mine (a DataType) was creating a DOM DocumentFragment, that you could
then use internally, pass on to other classes, or serialize. I believe both
use DynamicConfigurator. Regards, --DD
Yep, you can mix and match. DynaConf picks up only what's not explicitly
declared in the class. I'll send you my XmlFragment if you care for it. The
toString() is broken, since I had to modify Ant's DOMElementWriter to accept
a DOM Node instead of an Element. --DD
> -Original Message-
> Fr
And the piece which I consider the most debatable from this report...
Thankfully Peter Reilly seems to be a persistent person, more than myself
for sure, as the resistance to improvements to Ant so desperately necessary
for people like me who extend Ant so much, should not face so much
resistance
Title: build test fails
Just did an update, then '.\bootstrap.bat' followed by a 'build test', and got:
Testcase: testPrefixAddsDir(org.apache.tools.ant.taskdefs.ZipTest): Caused an ERROR
Unable to delete file P:\org_apache\ant\src\etc\testcases\taskdefs\test3.zip
P:\org_apache\ant\src\
I myself like quite a bit the task from Ant-Contrib by Peter
Reilly... Also does away with Ant's pour if/unless conditions on targets to
directly execute what needs to be done.
Peter even added the ability to have no target files, and just source files,
which are thus only checked for existence.
Hi Conor and fellow Anters,
Beside a couple comments below, I'd like to discuss the addition of another
feature to Ant for 1.6 wish I think would be very valuable, and make Ant
much more user friendly (in my setup at least).
We have quite a few projects here built using Ant, and very similar look
Namespaces is important to me. For example, my task infers the
current target name, whereas this feature was removed from the version now
checked in to Ant. I should be able to not have to rename it, and use it as
for example.
Of course, this will force me to update numerous builds (OK, only abo
g [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 26, 2003 9:56 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Ant 1.6 todo thoughts
>
> On Thu, 26 Jun 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote:
>
> > However, when an existing (custom) task/type is modified, Ant fa
; -Original Message-
> From: Steve Loughran [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 26, 2003 3:37 PM
> To: Ant Developers List
> Subject: Re: Ant 1.6 todo thoughts
>
> Dominique Devienne wrote:
> > Thanks for the quick answer Conor and Stefan. Glad to head this should
Today I evaluated the various ways I could download a file efficiently. So I
played with , using both the HTTP and FILE protocol, and with
(see build file below). The file I'm downloading is 38,448,695 bytes long.
The output of running each target twice is also shown below.
So what is this all ab
t: Re: About , , and buffer sizes
>
> On Fri, 27 Jun 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote:
>
> > I don't recall anybody noticing something like this.
>
> I didn't, that much is for sure.
>
> The buffer size comes at a cost (memory consumpti
I was wondering about that the day, and why there's no 'eval' keyword in
Java. It would be trivial for the compiler to generate the appropriate
reflection code on the fly... Maybe just because if would make programming
with reflection too easy and clean ;-) --DD
> -Original Message-
> From
Setting an explicit ID to the task is usually only used to be able to
reference that task from a
Technically, it's been created in September 2002 ;-) --DD
> -Original Message-
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 04, 2003 9:15 AM
> To: [EMAIL PROTECTED]
> Subject: Re: cvs commit: ant/src/main/org/apache/tools/ant/util/optional
> WeakishReference12.java
This discussing brings back the still pending issue of having a generic
if/unless on all tasks/types to name just an example...
failonerror, if/unless, ant:type, and some other attributes most likely,
control 'aspects' of the build, that should be dealt with in a single place!
Now that Ant is nam
Can't check.xml it from the Maven repository ;-) --DD
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 08, 2003 2:02 AM
> To: [EMAIL PROTECTED]
> Subject: AW: Checkstyle Audit
>
> And you need the checkstyle library.
> http://checkstyle.sourc
ard-wired
in Ant 1.6. And leave the generalization to a later date/release. --DD
> -Original Message-
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 08, 2003 10:05 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Patch] keep-alive feature
>
> On Tu
I've learned that anything slated for Ant 2.0 is doomed with failure...
And since ant:type is going in with 1.6, so should ant:if and co.,
IMHO that is ;-) --DD
> -Original Message-
> From: Steve Loughran [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 08, 2003 11:15 AM
> To: Ant Develope
You're kidding, right? How can that be? Isn't import a Task, with a
setFile(File) method? Don't the usual Ant rules apply? --DD
> -Original Message-
> From: peter reilly [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 16, 2003 10:51 AM
> To: Ant Developers List
> Subject: Re: problems wi
> -Original Message-
> From: peter reilly [mailto:[EMAIL PROTECTED]
>
> The problem is what the file should
> be relative to.
>
> The code tries to make the file relative
> to the current imported file or the build file
Which is the behavior I'd expect. Similar to #include "toto" in C/C+
Output your property to a properties file (), then read that
same property file back in using , but using a prefix (so has to
rename the properties on the fly since Ant properties are immutable), and
you now have prefixed properties with all variables expanded.
Not ideal, but two lines, and works.
a) I personally think that (2) is the least surprising answer,
and furthermore that
b) the effective basedir for the task to operate inside any
imported file should always be the outermost one.
Also,
c) Imported projects which have an explicit basedir specified
should result in a warning
This is indeed a valid use of knowledge of where an imported file was
imported from.
I still think (strongly) that the basedir of any imported file should be
ignored (with a warning if it's something else than ".", the default), and
always use the one of the top-level build.
To allow the use-case
I don't disagree with your scenario in the sense that it would break, but I
disagree that it's either a good usage of import or desirable.
I (strongly again ;) believe that imported build files should be designed to
be imported, and never used without being imported. I would even be
favorable (but
Did my other messages answer your questions??? --DD
> -Original Message-
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 24, 2003 10:09 AM
> To: [EMAIL PROTECTED]
> Subject: Re: ant 1.5.4 : Import
>
>
> Dominique Devienne wr
--DD
> -Original Message-
> From: Conor MacNeill [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 24, 2003 10:39 AM
> To: Ant Developers List
> Subject: Re: ant 1.5.4 : Import
>
> On Fri, 25 Jul 2003 01:23 am, Dominique Devienne wrote:
> >
> > I (strongly again ;) be
ist
> Subject: Re: ant 1.5.4 : Import
>
> On Fri, 25 Jul 2003 01:36 am, Dominique Devienne wrote:
> > Then have a look at what I did in the past two days to do something
> similar
> > ;-) I created an task that piggybacks on , and allows
> > returning properties and/
I answer Jose Alberto below about his specific points, but here are a
few others that were discussed:
1) Imported file build names
Actually, I don't care about the name of the imported file at all,
and as a build writer, I wish I didn't have to give the project a
name at all! When I imp
> -Original Message-
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
>
> > For example, let's say I have a compile target I want to import, and
> > I want to make it additionally call the "pre" target before and the
> > "post" target after.
>
> Then you don't want to import the target bu
I meant start with , and then specify 's behavior and
implement it. Too much work lately... --DD
> -Original Message-
> From: Dominique Devienne [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 29, 2003 9:12 AM
> To: 'Ant Developers List'
> S
Why don't you put the import *after* the
I liked Gmane, but you couldn't post like time I checked. Did that change. I
haven't heard anything on Apache-General or Ant-user/dev about explicitly
wanting to be dropped from it... --DD
> -Original Message-
> From: Antoine Levy-Lambert [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 3
Is-file and is-dir exist already. It's called , which is both a
Task and a Condition. --DD
> -Original Message-
> From: Morten Mortensen [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 30, 2003 2:48 PM
> To: 'Ant Developers List'
> Subject: Q: Implementing "conditions"
>
>
> Hi All,
>
In Ant 1.5.x, the Condition framework is not extensible without modifying
Ant's code. In Ant 1.6, just write a class that implements Condition,
it, and use it inside . Cannot get any simpler, right?
I haven't played with Ant 1.6 at all, so this is all in theory ;-)
If it doesn't work, complain to
Indeed ;-) What you demoed Conor is precisely the use case I need, which was
very much inspired by Knut's past posts. I also like Knut's
name better, as it's more explicit.
The one thing I'm not too sure about is the and
ones... Why are these needed? Property immutability is one
tenet of Ant we
I'm confused Peter about the reserved URIs. When you say ant:core and
antlib:, you really are talking about the URIs, not the
namespace prefixes, right?
If so, why is the ant:core URI so short, instead of the usual unique name
that result from using the DNS/URL name to Ant, with a version or date
I totally agree with everything you in this post Conor ;-) --DD
> -Original Message-
> From: Conor MacNeill [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 01, 2003 5:28 AM
> To: Ant Developers List
> Subject: Re: override
>
> On Fri, 1 Aug 2003 07:40 pm, Jose Alberto Fernandez wrote:
>
> -Original Message-
> From: Conor MacNeill [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 01, 2003 9:24 AM
> To: Ant Developers List
> Subject: Re: override
>
> On Fri, 1 Aug 2003 10:47 pm, Nicola Ken Barozzi wrote:
> > How can this thing be done while shielding interactions?
> >
>
> Y
> -Original Message-
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 01, 2003 10:27 AM
> To: [EMAIL PROTECTED]
> Subject: Re: override
>
> > and that renamed targets from a and b should not be
> > call-able directly from the command line, but only from within th
On second though, instead of renaming, why don't we use IDs, which are
common and well understood:
or better yet IMHO:
The notation feels very natural, and I don't see why one would need
to called a conflicting target (from an imported build file) from anywhere
but the same-
1 - 100 of 930 matches
Mail list logo
