DO NOT REPLY [Bug 29334] - Update Ant Manual to reflect latest changes to jakarta-commons/net for FTP task

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29334] New: - Update Ant Manual to reflect latest changes to jakarta-commons/net for FTP task

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29315] - task isn't found (in )

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29315] - task isn't found (in )

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29315] - task isn't found (in )

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29315] - task isn't found (in )

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23395] - Adding property element to xmlvalidate

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29329] - enhancement request

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29315] - task isn't found (in )

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29251] - [patch] add @url to task

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29315] - task isn't found (in )

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29329] New: - enhancement request

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29251] - [patch] add @url to task

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29326] New: - macrodef/task warning on

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24181] - Shutdown failing

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://issues.apache.org/bugzilla/show_bu

bug 27446 - fix avaliable

I've written a fix for this bug; but I cannot commit it. http://issues.apache.org/bugzilla/show_bug.cgi?id=27446 I pasted the "cvs diff" into the comment. Bret Weinraub

DO NOT REPLY [Bug 29251] - [patch] add @url to task

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://issues.apache.org/bugzilla/show_bu

Re: Open new command window for ANT task

Is there truly a need for actual, visible windows? Or do you just mean that you want the processes to be independent of the Java process that runs Ant? This is usually what people want and they seem to do fine with the or tasks--each has a spawn attribute that, when set to "true", creates (or,

Re: Open new command window for ANT task

Thank you to all for the advice! So far, the tack I am taking is: 1. writing a gui module that will redirect standard and error output to a JTextPane 2. having that module use Runtime.getRuntime().exec() to run a 'os' command (i.e. Jini) 3. put that into an Ant task.. So far I am up to the sec

cvs commit: ant/src/main/org/apache/tools/ant Project.java

mbenson 2004/06/01 07:51:55 Modified:src/main/org/apache/tools/ant Project.java Log: Tiny refactoring. Revision ChangesPath 1.168 +2 -2 ant/src/main/org/apache/tools/ant/Project.java Index: Project.java =

RE: Ant introspection and property resolution

-projecthelp Could only make nonsense if you have only some targets with description attributes. But I think I had read something about that on dev or users list ... But it might give some technical information? But I agree with you. > b) > > cmdline> ant -dependencies [build.xml] > >

RE: Ant introspection and property resolution

Try adding a couple of targets that "help" you find your information via some xsl transforms: a) targetlist.xsl -- http://www.w3.org/1999/XSL/Transform";> Found targets:

DO NOT REPLY [Bug 26312] - concat changes binary files

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24181] - Shutdown failing

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://issues.apache.org/bugzilla/show_bu

cvs commit: ant/src/main/org/apache/tools/ant/taskdefs ProcessDestroyer.java

bodewig 2004/06/01 06:33:25 Modified:src/main/org/apache/tools/ant/taskdefs Tag: ANT_16_BRANCH ProcessDestroyer.java Log: merge Revision ChangesPath No revision No revision 1.11.2.7 +2 -2 ant/src/main/

cvs commit: ant/src/main/org/apache/tools/ant/taskdefs ProcessDestroyer.java

bodewig 2004/06/01 06:33:10 Modified:src/main/org/apache/tools/ant/taskdefs ProcessDestroyer.java Log: JDK 1.3- Revision ChangesPath 1.18 +2 -2 ant/src/main/org/apache/tools/ant/taskdefs/ProcessDestroyer.java Index: ProcessDestroyer.java

cvs commit: ant/src/main/org/apache/tools/ant/taskdefs ProcessDestroyer.java

bodewig 2004/06/01 06:30:54 Modified:src/main/org/apache/tools/ant/taskdefs Tag: ANT_16_BRANCH ProcessDestroyer.java Log: merge Revision ChangesPath No revision No revision 1.11.2.6 +35 -27 ant/src/main/

DO NOT REPLY [Bug 29320] - The target object does not have getter for if/unless conditions.

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://issues.apache.org/bugzilla/show_bu

Re: Using Ant API to retrieve task/target information

Hi, I'm mailing only to say that Cristophe isn't alone. I have the same need here, obtain the target "if" and unless conditions, but I do not have a way to do this. I think that adding getters to Target is a great solution. How can we suggest this modification to the API, to get it in the next rel

DO NOT REPLY [Bug 29320] New: - The target object does not have getter for if/unless conditions.

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://issues.apache.org/bugzilla/show_bu

Re: Using Ant API to retrieve task/target information

On Tue, 1 Jun 2004, Christophe Labouisse <[EMAIL PROTECTED]> wrote: > So I'm wondering if using the Ant API as I do to peek into a project > is something which is ok albeit the API is currently lacking a few > things or the API should not be used the way I do? Your approach is fine, I'd say. I'm

RE: Using Ant API to retrieve task/target information

Jose Alberto Fernandez said: > Notice that you really cannot rely on the tasks allowing you to peek > at the information inside them. Remember that in principle ANT is a > component > framework and that more and more we spect ANT components to be provided > by third parties. So you cannot count on

RE: Ant introspection and property resolution

During ANT execution you have some limited access to the Project. I have script tasks that use this functionality get information about available targets and dependencies. But you cannot take hold of everything. Jose Alberto > -Original Message- > From: Ashwin S. [mailto:[EMAIL PROTECTED

RE: Using Ant API to retrieve task/target information

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > I think these getters arent there because we havent needed it > :-) Only the target class itself uses these information so > why putting them in? But if there is a need for having > getters outside I don´t see an obstacle while adding the

RE: Using Ant API to retrieve task/target information

I think these getters arent there because we havent needed it :-) Only the target class itself uses these information so why putting them in? But if there is a need for having getters outside I don´t see an obstacle while adding them ... the information are not unofficial ... Do you need more? J

Using Ant API to retrieve task/target information

Hi, I'm the writer of the Grand tool (http://www.ggtools.net/grand) and since I came upon some issues with the Ant API I'd like to have some more or less "official" advice about the way I use it. I started Grand shortly after Ant 1.6.0 was released since the visualization tools I used where all b

DO NOT REPLY [Bug 29178] - InstantiationException with Ant 1.6.1 not with Ant 1.5.4

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://issues.apache.org/bugzilla/show_bu

RE: Ant introspection and property resolution

> Is there a way of actually introspecting a build file via > ant. The introspection should help expose details such as > a) all targets in an build file > b) dependency trees for targets > > and many other such details that might be useful to seasoned > ant-users. > > I am envisaging its use a

DO NOT REPLY [Bug 29315] - task isn't found (in )

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://issues.apache.org/bugzilla/show_bu

[Ant Wiki] Updated: WikiSandBox

Date: 2004-05-31T23:43:06 Editor: StefanBodewig <[EMAIL PROTECTED]> Wiki: Ant Wiki Page: WikiSandBox URL: http://wiki.apache.org/ant/WikiSandBox spam Change Log: -- @@ -22,8 +22,6 @@ [EMAIL PROTECTED

Ant introspection and property resolution

Is there a way of actually introspecting a build file via ant. The introspection should help expose details such as a) all targets in an build file b) dependency trees for targets and many other such details that might be useful to seasoned ant-users. I am envisaging its use as follows: a) cmd

DO NOT REPLY [Bug 29315] New: - task isn't found (in )

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://issues.apache.org/bugzilla/show_bu