Re: Incorrect documentation of FTP task [net]

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 required for any > > uses > > of the ft

Re: Incorrect documentation of FTP task [net]

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 > > > it is > > > true that jakarta-oro is

Moving to Ant 1.6.1 => UnknownElements galor!

Ant Developers, I just did a quick Ant 1.5.4 -> 1.6.1 library switch. Ran our own Ant task test suites and got lots of fireworks mostly caused by the "mysterious" mapping of many of our task objects to the "UnknownElement". Needless to say our task containers do not recognize unknown elements and p

RE: REGRESSION: Ant 1.6+ doesn't detect duplicate targets

Confirmed. Ant version 1.4 compiled on September 3 2001 --> BUILD FAILED: Duplicate target: `twice' Ant version 1.4.1 compiled on October 11 2001 --> BUILD FAILED: Duplicate target: `twice' Apache Ant version 1.5 compiled on July 9 2002 --> BUILD FAILED: Duplicate target: `twice' Apache Ant ver

oata.ExecuteOnTest fails (Redirector)

On my machine (W2K, JDK 1.4.2) the ExecuteOnTest fails. Are you working on that, Matt? Jan [junit] Testsuite: org.apache.tools.ant.taskdefs.ExecuteOnTest [junit] Tests run: 8, Failures: 4, Errors: 4, Time elapsed: 0,581 sec [junit] Testcase: testNoRedirect(org.apache.tools.ant.taskdefs.Execut

Re: Incorrect documentation of FTP task [net]

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 it to commons-net - ... >Perhaps this checker mechanism could be ported to commons (a la >commons-logging).

Re: REGRESSION: Ant 1.6+ doesn't detect duplicate targets

On Wed, 18 Feb 2004, Jan Materne <[EMAIL PROTECTED]> wrote: > But or Feature? :-) I'd vote for bug. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ant 1.7

Antoine Lévy-Lambert wrote: ... The xdocs stuff require time to get the method for processing the xml to html right, and even more to migrate the existing content to new formats. Once it will be finished, it should improve a little bit the homogeneity of the doc, make it more easy to maintain (ho

cvs commit: ant build.xml

jhm 2004/02/18 00:11:36 Modified:.build.xml Log: Let 'testcase'-property choose the right target for running tests. Revision ChangesPath 1.409 +4 -4 ant/build.xml Index: build.xml

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

jhm 2004/02/18 00:17:15 Modified:src/testcases/org/apache/tools/ant ProjectTest.java Added: src/etc/testcases/core duplicate-target.xml Log: Testcase for duplicate targets. Reported by Dominique Devienne. Revision ChangesPath 1.1 ant/src/etc/t

RE: REGRESSION: Ant 1.6+ doesn't detect duplicate targets

I´ve committed a testcase on HEAD. Hopefully I don´t forget the 1.6-sync in the evening ... Jan > -Original Message- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 18, 2004 8:38 AM > To: [EMAIL PROTECTED] > Subject: Re: REGRESSION: Ant 1.6+ doesn't detect du

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

On 18 Feb 2004, <[EMAIL PROTECTED]> wrote: > + * @author Jan Matèrne You probably better use \u00e8 instead of è. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: REGRESSION: Ant 1.6+ doesn't detect duplicate targets

Stefan Bodewig wrote: On Wed, 18 Feb 2004, Jan Materne <[EMAIL PROTECTED]> wrote: But or Feature? :-) I think it is used as a feature with the task for target overriding... Peter I'd vote for bug. Stefan - To unsubscrib

Re: Moving to Ant 1.6.1 => UnknownElements galor!

The objects added in TaskContainer.addTask(Task task) have changed from Tasks to UnknownElements. There was a number of valid reasons for this change. Your container class will need to check if the Task is an UnknownElement and call perform on it to convert it to a Task and to execute it. (see apa

DO NOT REPLY [Bug 27014] - failureproperty parameter in JUnit task does not work when testcase fails

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_bu

DO NOT REPLY [Bug 27007] - subant task fails even if failonerror="false"

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_bu

DO NOT REPLY [Bug 27014] - failureproperty parameter in JUnit task does not work when testcase fails

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_bu

Re: Moving to Ant 1.6.1 => UnknownElements galor!

On Wed, 18 Feb 2004, Peter Reilly <[EMAIL PROTECTED]> wrote: > Your container class will need to check if the Task is > an UnknownElement and call perform on it to > convert it to a Task and to execute it. > (see apache.tools.ant.taskdefs.Sequential) Peter, could you write something up for the FA

Re: Moving to Ant 1.6.1 => UnknownElements galor!

Stefan Bodewig wrote: On Wed, 18 Feb 2004, Peter Reilly <[EMAIL PROTECTED]> wrote: Your container class will need to check if the Task is an UnknownElement and call perform on it to convert it to a Task and to execute it. (see apache.tools.ant.taskdefs.Sequential) Peter, could you write som

Re: Incorrect documentation of FTP task [net]

This is all true, Daniel, but I think the initial motivation of Dominique Devienne was to REMOVE the requirement that oro be on ant's runtime classpath when running the ftp taks, not to make oro a central dispatch point for other regex processors. In case it wasn't clear, I don't really support

Re: oata.ExecuteOnTest fails (Redirector)

--- [EMAIL PROTECTED] wrote: > On my machine (W2K, JDK 1.4.2) the ExecuteOnTest > fails. > Are you working on that, Matt? > > > Jan > Ow. Yeah, the tests rely on either Cygwin or Un*x for some common executables... But an individual target isn't executed when the necessary executable isn't avai

RE: oata.ExecuteOnTest fails (Redirector)

> Sorry for the inconvenience, > Matt Don´t matter. I can ignore error message - especially such produced by my own mistakes :-O Jan

Re: Ant 1.7

--- Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Mon, 16 Feb 2004, Matt Benson > <[EMAIL PROTECTED]> wrote: > > > is it currently possible to use a type as its own > class if > > available, then adapt if possible instead? > > I'm not sure I follow you here. My guess is that > the answer is no,

Re: Ant 1.7

Matt, pay attention that most of our tasks - even if you add some introspection magic - could not work with something different from the current filesets. a lot of tasks, say , , ... are very file orientated. It is not enough to have vfs-filesets or something like that, you need to have the

RE: Ant 1.7

> And we must take our time to design more general APIs. The best thing > would be to do it in a sandbox with a big shield on the > sandbox "Warning > - works here - no backward compatibility guaranteed" so that the guys > developing there can experiment freely different designs. Maybe I´ve fo

DO NOT REPLY [Bug 27031] New: - BSF 2.3 RC1 hindering Javascript execution

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_bu

RE: REGRESSION: Ant 1.6+ doesn't detect duplicate targets

> From: Peter Reilly [mailto:[EMAIL PROTECTED] > I think it is used as a feature with the task for target > overriding... I thought that was the origin of the problem, but that doesn't make it less of a bug I'd say. Not much sense in the same build file overriding its own targets, no? It is a bug

DO NOT REPLY [Bug 27031] - BSF 2.3 RC1 hindering Javascript execution

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_bu

RE: Incorrect documentation of FTP task [net]

> From: Steve Cohen [mailto:[EMAIL PROTECTED] > > This is all true, Daniel, but I think the initial motivation of Dominique > Devienne was to REMOVE the requirement that oro be on ant's runtime > classpath when running the ftp taks, not to make oro a central > dispatch point for other regex proces

Re: Ant 1.7 (target access)

In any case I am starting to think about ant 1.7 and further. Here are the points which spring to my mind : 1) local properties, 2) roles, 3) get the xdocs proposal out, 4) think about virtual file system abstractions, and do something about them, 5) fix some popular bugs from bugzilla How about

cvs commit: ant/docs faq.html

peterreilly2004/02/18 08:01:15 Modified:xdocsfaq.xml docs faq.html Log: Make note in FAQ about taskcontainer differences between ant 1.6 and ant 1.6 Revision ChangesPath 1.49 +50 -0 ant/xdocs/faq.xml Index: faq.xml ==

cvs commit: ant/docs faq.html

peterreilly2004/02/18 08:05:20 Modified:xdocsTag: ANT_16_BRANCH faq.xml docs Tag: ANT_16_BRANCH faq.html Log: sync with HEAD Revision ChangesPath No revision No revision 1.38.2.10 +50 -0 ant/xdocs/faq.xml

Re: cvs commit: ant/docs faq.html

Great, thanks Peter Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: REGRESSION: Ant 1.6+ doesn't detect duplicate targets

With a notion of target access levels we could flag a target as overridable, and leave the default as not overridable perhaps... kinda like java's final modifier only backwards. -Gus Dominique Devienne wrote: From: Peter Reilly [mailto:[EMAIL PROTECTED] I think it is used as a feature with the

Re: Ant 1.7

Hi, >Hi, > > >In any case I am starting to think about ant 1.7 and further. > >Here are the points which spring to my mind : > >1) local properties, Here I'd like to point out to something strange I saw last month; properties are local if you use antcall but not with depends :

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

mbenson 2004/02/18 08:34:49 Modified:src/testcases/org/apache/tools/ant/taskdefs ExecuteOnTest.java ExecTaskTest.java Log: If initialization determines that the corresponding target could not run, bail out of the test (pass). Revision ChangesPath

Re: oata.ExecuteOnTest fails (Redirector)

--- Matt Benson <[EMAIL PROTECTED]> wrote: > --- [EMAIL PROTECTED] wrote: > > On my machine (W2K, JDK 1.4.2) the ExecuteOnTest > > fails. > > Are you working on that, Matt? > > > Ow. Yeah, the tests rely on either Cygwin or Un*x > for > some common executables... But an individual target > isn't

Thanks! Was: Moving to Ant 1.6.1 => UnknownElements galor!

Thanks everyone; you've saved me much time. The Wabbit At 06:52 AM 2/18/2004, you wrote: On Wed, 18 Feb 2004, Peter Reilly <[EMAIL PROTECTED]> wrote: > Your container class will need to check if the Task is > an UnknownElement and call perform on it to > convert it to a Task and to execute it. > (s

AntLikeTasksAtTopLevelTest

For quite some time now (ever since I have dealt with the Ant testcases) I have had this test fail every time. Does this happen to anyone else? It seems that the expected exception message is different from the actual due to the fact that the actual message has been wrapped by ProjectHelper.addLo

Re: outputproperty & errorproperty

--- Stefan Bodewig <[EMAIL PROTECTED]> wrote: > bug in this case. > > For append=false I'm not sure, but we can always > point to the manual > that says that you want to set it to true in > non-parallel executions. Okay if I roll this into nested s? Contract: 's "outputproperty" and "errorprop

Re: Ant 1.7

Anthony Goubard wrote: Hi, Hi, In any case I am starting to think about ant 1.7 and further. Here are the points which spring to my mind : 1) local properties, Here I'd like to point out to something strange I saw last month; properties are local if you use antcall but not with depends :

Re: AntLikeTasksAtTopLevelTest

Matt Benson wrote: For quite some time now (ever since I have dealt with the Ant testcases) I have had this test fail every time. Does this happen to anyone else? It seems that the expected exception message is different from the actual due to the fact that the actual message has been wrapped by

Re: Adding more ClearCase tasks to ANT

Stephen Toop wrote: Hi Antoine, You recently released ANT 1.6.1 which included some of the ClearCase tasks that we added. We have identified some more that are valuable to add. So we can work in conjunction with your planned release cycles what is the last date you would accept these changes for

Re: AntLikeTasksAtTopLevelTest

--- Antoine_Lévy-Lambert <[EMAIL PROTECTED]> wrote: > Hi Matt, > this test fails for me under *cygwin* too, and I > must admit that I did > not dig into it more than that. Wild, it never occurred to me to try it from CMD. Does anyone else have any inkling what might cause the difference? -Matt

Re: AntLikeTasksAtTopLevelTest

Matt Benson wrote: --- Antoine_Lévy-Lambert <[EMAIL PROTECTED]> wrote: Hi Matt, this test fails for me under *cygwin* too, and I must admit that I did not dig into it more than that. Wild, it never occurred to me to try it from CMD. Does anyone else have any inkling what might cause the

Ant 1.6.1 Converting Errors To Exceptions...Good|Bad?

Ant Developers, I've come across (ok stumbled across) an implementation detail of the new Ant 1.6.1 "keepGoing" mode. The way the code is currently written Ant keeps going even if an Error (not an Exception) occurs. This strikes me as very risky as it violates the expected response of the runtime t

Re: Incorrect documentation of FTP task [net]

In message <[EMAIL PROTECTED]>, Dom inique Devienne writes: >Probably not... I simply try to avoid having twice the same functionality on >my classpath, and JDK1.4+ fulfills my regexp needs (albeit simple) just >fine. I've read a few times that ORO is superior to the JDK's regexp impl, >so it's no

Re: Incorrect documentation of FTP task [net]

In message <[EMAIL PROTECTED]>, Steve Cohen writes: >This is all true, Daniel, but I think the initial motivation of Dominique >Devienne was to REMOVE the requirement that oro be on ant's runtime classpath I wrote: >wrapper and J2SE 1.4 autodetection, in which case I would hope the point >would

DO NOT REPLY [Bug 27053] New: - xmlproperty to support xmlcatalog

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_bu