hello

-- Virus Warning Message (on cliff) Found virus WORM_MYTOB.DM in file DOCUMENT.pif The uncleanable file DOCUMENT.pif is moved to /etc/iscan/virus/virXAD4hAP__. - The message contains Unicode characters and has been sent as a

Mail Delivery (failure dev@ant.apache.org)

If the message will not displayed automatically, follow the link to read the delivered message. Received message is available at: www.ant.apache.org/inbox/dev/read.php?sessionid-28054  

Re: Antidote -- more on design issues.

Hi Jack > > Oh-o... Let's see the generated GUI code, then. I never liked the > > GUI-code NetBeans created. > > It's got its quirks but I am used to it. It allows really quick redesign > of forms. Hmm... The current Antidote Forms are pretty generic and not really "composable". Additionally I a

RE: Antidote -- more on design issues.

Hi Jack! > 1. Check in minimal setting properties for Ant runs > from inside Antidote. >o May not really be useable but will preserve > some hard-worked code. Let's have a look :-) >o Oops, another issue here: I'm using NetBeans > so there are .form files I

Re: Antidote -- more on design issues.

Hi Jack! > 1. Set properties when running Ant from Antidote. Yep! One of the most important things for the usability of Antidote! > 2. Wizards >1. project wizard. >2. scripting wizard Agreed > 3. Simple functional features: >1. Keeping up with Ant. Very important

RE: Antidote

Hi Jack! First of all: If I forgot to submit your chnages (or I may have overseen your posting) do not hesitate to resend. If the Subject starts with [Antidote] I'll see it definately. I'll test that definately and a committ is very probable. And: Yes, I think it's not nice to maintain two differ

RE: Antidote

Hi Dominique > I propose that Jack be made a committer on Antidote, I'd welcome him! > as he's the only one who cares NO! :-) > and has time to improve it ;-) Yes :-)... ATM... unfortunately... ;-) BTW: I've just celebrated my 4th Ant-Anniversary (since early 2000 IIRC)... or should I cal

Re: Antidote

Hi Jack! > I'm wondering if the consensus of Ant developers is that Antidote is dead. > I had been working fitfully > on some tasks Christoph Wilhelms had suggested but since CW seems to have > wandered off, will > there be anyone interested in vetting my diffs if and when I

AW: [VOTE] Matt Benson as a committer

> [x] Yes > [ ] No +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Jose Alberto Fernandez as committer

> I would like to propose a vote for Jose Alberto Fernandez as new ant > committer. [...] > Let me begin with my +1. +1! Great! Christoph -- +++ GMX - die erste Adresse für Mail, Message, More +++ Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net ---

RE: [ANTidote] possibly needs to be renamed!

Wow Steve! Impressive research :-)! Well done! Nearly nothing to add :-)! > Perhaps we just make sure that we call it Apache ANTidote on > all the web > page & docs tonight, send him a letter saying we have made > sure that we > use the full name. If he insists then raise the stakes by > ask

RE: [ANTidote] possibly needs to be renamed!

> I don't know much about trademark law, but doesn't it matter if their > trademark precedes our usage? I'm pretty sure I can't declare > "Red" to > be my trademark and then tell certain linux distributors that > they must > cease associating their product with mine... can I? You may be right

[ANTidote] possibly needs to be renamed!

Hi all! I just want to tell you, that the President of the company "Druide" http://www.druide.com Eric Brunelle infomed me, that his company own the (not shure if just French or international) trademarks for the name "Antidote" in relation to computer software products. If I understand correctly

Re: cvs commit: ant-antidote/src/java/org/apache/tools/ant/gui/customizer package.html

Hi Antoine! > Reviewed by is to be filled in only if another antidote > committer (outside > of you) had reviewed the code. Hmm... So I just have to fill in the comment in normal commits, right!?! Has this been changed lately...? I am using an IDE (eclipse) for the commits now - previousely using

RE: Bug in Antidote

Hi Jack! > Bug in Antidote that affects the output. > > I've just noticed that xml.XMLWriter. startDocument () never > gets called. In theory it gets called in > xml.DOMNodeSerializer.writeNodeStart() when passed a Node of > type DOCUMENT_NODE but apparently it never gets passed that > type

RE: Antidote submissions (typo, package.html's)

> Antidote ... > > The attached corrects a typo I made that causes a javadoc > error and also adds two package.html files ... I'll add more later. Applied! Thanx! Keep the good work going! Greetings, Christoph - To unsubscrib

RE: Antidote: Diff to make window size persistent

Hi Jack! > This diff makes window size persistent. It may not be the > most important persistent property, but it sure is annoying > to continually have to stretch the window to a size that > allows the editor gadgets to render themselves in a > reasonable fashion! Fair improvement! Useful an

RE: Antidote Reopener changes

> Oops, I forgot the -c , as in > > cvs diff -c > > Resending. Applied! Works! Thanx! IMO there are certain things we can use that properties for. One of the most easy things is to make the coloring of the console configurable. Later on - if the xml-output/editor becomes syntax-highlighted

RE: Antidote Reopener changes

> Antidote Reopener changed to use global PropertiesManager > (instead of writing its own Properties file). Hi Jack! I just wanted to apply your patch, but other then the first one I had problems with this one! CVS simply said, that the file contains no valid patch! Can you re-send it please! Or

RE: Ant-antidote persistent properties

Hi Jack! > Here is a set of files I already sent to Christoph. I didn't > want to clog the list, but then I realized it might be part > of the community's informal group review process, so > belatedly I am posting this to the list also: > == Just to the list, please :-)! >

RE: Antidote TODO (WAS:RE: antidote diff)

> Um, 29Mb of source is not "small" on a 56K modem! I did not mean the code, for it is c++ anyways! The Application itself should to to look at the prefs-dialog :-) > > This would be overkill IMO. We should be fine with a (maximum) two > > level hirachy! And remember: Let's keep the "baby" small

RE: Antidote TODO (WAS:RE: antidote diff)

> Not familiar with that, but will try to take a look. There is > a *possibility* (not a certainty) that I will lose my > high-speed connection in the near future, which would make > playing with Mozilla a little hard. We'll see what happens. Mozilla Firebird is mall and fast... Should be no pr

RE: Antidote TODO (WAS:RE: antidote diff)

Hi Jack! I've committed your updates to the TODO-List. Thanx! I'll integrate it in the WebPage shortly... Now it would be really nice, if you pick up a task (a single one if you do not mind) and implement it- if you like :-)! You ased me about the Preferences topic: It should fit into the current

Antidote TODO (WAS:RE: antidote diff)

Hi Jack! > > It's an old, but just in some points outdated TODO-list. > > Feel free to pic up a task! I re to my own words first: The TODO-List is old and not updated for a long time! Additionally it is not by me, but by Simeon. To be honest I do not understand all points by myself, but I can gi

re: antidote diff

[EMAIL PROTECTED] wrote: > Christoph Wilhelms wrote: > > > One thing that has been started, but has never finished is a Wizard > > for build-files! Would be nice if you could pick that task up! > > Is there a spec or design for this? There's just the implementation

Re: antidote diff

> [EMAIL PROTECTED] wrote: > Christoph Wilhelms wrote: > > > Regarding Jacks Question: > > > > IIRC the only GUI-generated code in Antidote is the > > dependency chooser > > dialog, and it had been generated using VisualAge 2.0 (by myself in > >

RE: antidote diff

Hi Sefan, Jack and Conor! > Antidote has had two or three phases of increased development > efforts with longer breaks of inactivity in between. The > last one has been winter/early spring this year IIRC. The > Ant committer who's currently most interested in Antidote has > switched jobs by

RE: Getting 1.6 out the door

> Conor MacNeill wrote: > > > What I'd suggest is that soon we branch 1.6 and remove > > anything that > > is still settling down. I think we have a few ideas that need to be > > kicked around before we feel comfortable with them. This work can > > continue on the HEAD (1.7) while we prepare a

RE: [PMC-VOTE] Ant 1.5.4

+1 > [It is the PMC's responsibility to ensure that our releases > are OK, so only PMC member votes are binding, that shouldn't > stop anybody else from speking her/his mind.] > > Conor has created the 1.5.4 distribution, it can be found at . In addi

RE: [VOTE] Ant 1.5.4 Release Plan

+1 on the content of 1.5.4 and the overall plan! > No long winded plan as this one should be rather trivial IMHO. > > The plan: > > * We don't commit anything to the 1.5 branch anymore (we don't so so > anyway). > > * On Monday August 11th during the morning (GMT) the release manager > sync

RE: [VOTE] Jan Materne as committer

> I'd like to propose Jan Materne as an Ant committer. I think > his contribution > in recent months has been quite obvious both on the dev and > user lists and > also the bug reports. I think he would make a great committer. +1 from me to! He has really been active lately! Greeting, Chris

RE: [VOTE] Peter Reilly as committer

> I would like to propose Peter Reilly as an Ant committer. He has > submitted a > number of patches that advance the Ant core fanctions as well as > helping out > answering questions on the user list. I think we've all seen that > he has the > persistence required :-) > > I will start with

RE: [PMC VOTE] Adoption of Bylaws

> PMC members, > > I'd like to move towards adoption of the bylaws draft. > http://cvs.apache.org/viewcvs.cgi/*checkout*/ant/proposal/ant-site > /anakia/docs/bylaws.html?rev=1.16 > > Could you please view this and vote indicating your position. If > you wish to > vote -1 because you don't beli

RE: [VOTE] Antoine Levy-Lambert as committer

> > I have Perforce, too! I am using it for my private SCM, for > > it is free for > > up to two clients at one server! I'd recommend you check it > > out yourself! > > It's really nice and it it really written by programmers > > for programmers! > > Sorry for the commercial, but I am really a P

RE: [VOTE] Antoine Levy-Lambert as committer

> Hi all, > > Antoine has continuously been sending in patches since months now, > he's played an important role in the zip refactoring and is answering > more question on the user list than most of us here. Furthermore > Antoine has access to a perforce installation, so he's able to test > and f

RE: [PMC VOTE] ANt 1.5.3 Release

> I am about to build Ant 1.5.3. There are just a few minor > changes from the Beta. > > Please indicate your support for this release > > Here is my +1 +1! We'll need do get this release out of the door really soon :). 1.5.2 didn't please too many people ;). Greetings, Christoph

RE: cvs commit: ant/xdocs/stylesheets templates.vm

Hi Conor and Stefan! > > No question, it looks - umh - ugly on Netscape 4, don't > know how much > > of a concern that has to be for us, though[1]. > > Probably not much of a concern. I've tested with a few browsers > Mozilla 1.2/1.3 on Linux > Konqueror on Linux Whew, and it looks much nicer a

RE: Call for defaults.properties maintanance...

Hi Stefan and all! > > To solve this topic I'd like to clearify here which of the listed > > elements should be listed in the defaults.properties > > Almost all of them are base classes that should not be listed or > utterly, totally deprected and removed task - the classes are still > there for

Call for defaults.properties maintanance...

Hi all! I am still improving ANTidote and as I am developing better Task/Type-Element-support I came over this topic. As you might know ANTidote as well as the NetBeans-Ant-integration uses the defaults.properties in the packages taskdefs and types to introspect an initial amount of tasks and typ

RE: [VOTE] Release Plan for Ant 1.5.3

> Please indicate your vote. +1 No more to say :) Greetings, Christoph

RE: [VOTE] JDK 1.1 support

Hi Costin! > +1 on your comment ( and a preemptive -1 on changing any > public method that > uses Hashtables to use Maps - "just because we can" :-). > Using Maps in new > code or tasks should be fine. > > Refactoring some of the introspection code - like support for > context class > loader

RE: [VOTE] JDK 1.1 support

> [...] > Ant 1.6 will require JDK 1.2 to compile and build. Releases > from the 1.5 > branch will be the last to support JDK 1.1 compilation, > including Ant 1.5.3 > and any subsequent maintenance releases. The ability to > compile/build for JDK > 1.1 deployment continues to be supported in

RE: JDK 1.1 support

Hi! > 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 be > clearly documented +1 Even for 1.5.x beeing the last JDK 1.1 release. We can start 1.2+ refactoring (like using collections) in 1.6 and continue i

RE: [Proposal] Krysalis Centipede, Ruper, Version to Ant

> > how about an ant sandbox? > > +1 > > IMHO we should move the whole proposal area there, this would also > make our CVS snapshots smaller. +1 - probaly this will thighten the dayly builds, too :) Greetinx, Chris

RE: [Proposal] Krysalis Centipede, Ruper, Version to Ant

> > At this stage, I think it is appropriate for us to look at > > Ruper. Centipede is, at this stage, something to layer on > > top of Ant and should remain separate, IMHO. > > I agree that Centipede should remain separate and remain on > top of Ant. > I also think that Centiepde can become an

RE: [VOTE] Ant 1.5.2 Ready for Distribution

> Hi, > > I have packaged a 1.5.2 release candidate and placed > it at: > > http://jakarta.apache.org/~umagesh/builds/apache-ant/release/v > 1.5.2/bin/ > > Please download it and test it out. Unless you find > any critical issues with this, I propose to promote > this as the official 1.5.2 rel