Re: Why the latest build requires explicit for

On Thu, 4 Sep 2003 07:25 am, Alexey N. Solofnenko wrote: > Is it possible to add '-explain' option to see the real reason why a > task cannot be instantiated? > Have you run with -debug? Conor - To unsubscribe, e-mail: [EMAIL P

Re: Why the latest build requires explicit for

Did you try -debug? On Wednesday, September 3, 2003, at 05:25 PM, Alexey N. Solofnenko wrote: Is it possible to add '-explain' option to see the real reason why a task cannot be instantiated? - Alexey. - To unsubscribe, e-mai

Re: Why the latest build requires explicit for

Did you try -debug? On Wednesday, September 3, 2003, at 05:25 PM, Alexey N. Solofnenko wrote: Is it possible to add '-explain' option to see the real reason why a task cannot be instantiated? - Alexey. - To unsubscribe, e-mai

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

> bodewig: could you please also update docs/manual/running.html? will do that > What about a -H for -projecthelp??? Sounds more explicit... --DD That´s why I started the discussion before changing the code. I don´t think that that would be useful. Until now -D is the only upper case option. An

DO NOT REPLY [Bug 22919] - cvs does not execute if cvs bin directory in path statement is enclosed in quotes.

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: Why the latest build requires explicit for

Erik Hatcher wrote: Did you try -debug? On Wednesday, September 3, 2003, at 05:25 PM, Alexey N. Solofnenko wrote: Is it possible to add '-explain' option to see the real reason why a task cannot be instantiated? - Alexey. better yet, ant -diagnostics to see what tasks are present --

Re: .net tasks and mono

On Wed, 03 Sep 2003, Steve Loughran <[EMAIL PROTECTED]> wrote: > I proose, therefore, that we pull all 'helpful' auto referencing > from the ant task because it wasnt needed on windows, and broke > mono. Then we can get rid of that extra attribute we hacked in for > mono support. +1 Stefan

Re: Why the latest build requires explicit for

On Wed, 03 Sep 2003, Alexey N. Solofnenko <[EMAIL PROTECTED]> wrote: > I saw somewhere that Rhino is required for script task, but it > actually requires BSF. Wherever you've seen that, Rhino is not required by

cvs commit: ant ReleaseInstructions

bodewig 2003/09/04 00:28:57 Modified:.ReleaseInstructions Log: Some updates, machine name changes, adhere to Apache's beta distribution policy ... Revision ChangesPath 1.17 +12 -15ant/ReleaseInstructions Index: ReleaseInstructions

Re: antcall and build.xml being modified.

On Wed, 3 Sep 2003, Larry Shatzer <[EMAIL PROTECTED]> wrote: > When it is run the output is as follows: As long as you are not using an OS like Windows that locks your build file while Ant is running. > I figured the output would have been this: is just a thin layer on top of , it reparses the

Re: Getting 1.6 out the door

On 09/03/2003 06:33 PM Gus Heck wrote: As I've been saying all along, lets just introduce a new (unique) notion for attribute/variable expansion (at use time rather than definition time), which is something new in Ant anyhow. No (or less?) backward compatibility issues, and makes it plain and obvio

DO NOT REPLY [Bug 22930] New: - New update mode in zip (and related) 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://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 22923] New: - Out-of-date JBuilder information

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

cvs commit: ant/docs/manual/CoreTasks antcall.html

bodewig 2003/09/04 03:57:33 Modified:docs/manual/CoreTasks antcall.html Log: Clarify antcall in presence of self-modifying build files. Revision ChangesPath 1.17 +5 -0 ant/docs/manual/CoreTasks/antcall.html Index: antcall.html

[GUMP] Test Failure - Ant

030904/js.jar:/home/rubys/jakarta/beanshell/dist/bsh-20030904.jar:/home/rubys/jakarta/beanshell/dist/bsh-bsf-20030904.jar:/home/rubys/jakarta/beanshell/dist/bsh-classpath-20030904.jar:/home/rubys/jakarta/beanshell/dist/bsh-commands-20030904.jar:/home/rubys/jakarta/beanshell/dist/bsh-core-200309

cvs commit: ant/docs/manual ide.html

conor 2003/09/04 04:16:25 Modified:docs/manual ide.html Log: Update IDE info to include JBuilder PR: 22923 Revision ChangesPath 1.11 +75 -29ant/docs/manual/ide.html Index: ide.html ==

DO NOT REPLY [Bug 22923] - Out-of-date JBuilder information

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: antcall and build.xml being modified.

On Thu, 4 Sep 2003 05:31 pm, Stefan Bodewig wrote: > > > If anything, I think this should be documented, since it is a > > gotcha. > > Will do. > I would like to have this documented as "undefined". I don't think we should be forced to reparse a build file in future just because we do so now. A

cvs commit: ant/xdocs index.xml

bodewig 2003/09/04 04:39:58 Modified:docs/manual Tag: ANT_15_BRANCH ide.html xdocsTag: ANT_15_BRANCH index.xml Log: Merge changes from HEAD to make them appear at the website Revision ChangesPath No revision No revi

Re: antcall and build.xml being modified.

On Thu, 4 Sep 2003, Conor MacNeill <[EMAIL PROTECTED]> wrote: > I would like to have this documented as "undefined". I agree and will change my blurb accordingly. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additiona

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

conor 2003/09/04 04:58:02 Modified:src/main/org/apache/tools/ant/taskdefs Manifest.java Log: Make sure continuations of multi valued attributes (Class-Path) are added to the correct instance PR: 22816 Submitted by: Dan Douglas Revision ChangesPath 1.47 +

DO NOT REPLY [Bug 22923] - Out-of-date JBuilder information

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 22589] - Empty Output to File from Java Task if Java 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 22733] - Mistake When I use build

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

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

bodewig 2003/09/04 04:46:03 Modified:src/etc/testcases/taskdefs ant.xml src/main/org/apache/tools/ant Project.java Target.java src/main/org/apache/tools/ant/taskdefs Ant.java src/testcases/org/apache/tools/ant/taskdefs AntTest.java Log: Ca

cvs commit: ant/docs/manual/CoreTasks antcall.html

bodewig 2003/09/04 04:45:25 Modified:docs/manual/CoreTasks antcall.html Log: leave it undefined to avoid feature lock-in Revision ChangesPath 1.18 +2 -3 ant/docs/manual/CoreTasks/antcall.html Index: antcall.html ===

DO NOT REPLY [Bug 22816] - Continued multiple Class-Path: manifest attributes not parsed

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 22444] - Trailing slash in property location eaten

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: antcall and build.xml being modified.

> -Original Message- > From: Conor MacNeill [mailto:[EMAIL PROTECTED] > > Self-modifying builds are not a practice I would recommend. I actually disagree with that statement somewhat. As long as the self-modification is controlled and static, it's actually a good and powerful way to build

Re: Why the latest build requires explicit for

Hello, -diagnostics reported that scriptdef is not available (still without explanation), but I can add to make it work. Without there is only a message "Could not load class (org.apache.tools.ant.taskdefs.optional.script.ScriptDef) for type scriptdef". An exception stack trace would be nice

RE: antcall and build.xml being modified.

> -Original Message- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 04, 2003 12:32 AM > To: [EMAIL PROTECTED] > Subject: Re: antcall and build.xml being modified. > > > On Wed, 3 Sep 2003, Larry Shatzer <[EMAIL PROTECTED]> wrote: > > > When it is run the out

RE: antcall and build.xml being modified.

> -Original Message- > From: Conor MacNeill [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 04, 2003 2:45 AM > To: Ant Developers List > Subject: Re: antcall and build.xml being modified. > > Self-modifying builds are not a practice I would recommend. > Let me clarify, the build sc

RE: antcall and build.xml being modified.

> -Original Message- > From: Dominique Devienne [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 04, 2003 6:54 AM > To: 'Ant Developers List' > Subject: RE: antcall and build.xml being modified. > > I do agree about not locking Ant into forcing reparsing if the > build file is changed

DO NOT REPLY [Bug 22904] - [Patch] to download some third party libraries (not complete)

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