cvs commit: ant/docs/manual/api index.html

stevel 2005/01/19 15:15:26 Modified:docs/manual coretasklist.html docs/manual/CoreTasks nice.html docs/manual/api index.html Added: docs/manual/CoreTasks libraries.html Log: gave up on xdoc updates for now; did the libraries task by hand. minor

DO NOT REPLY [Bug 33169] New: - ClearCase update produces verbose output---request standard output suppression feature

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: Need a target meta data for parallel executor.

Currently the executor uses only dependency information - if target A depends on B, A can be executed only after B is completed. If there is no direct on indirect dependency between two targets - they can be executed in parallel. I also wanted to implement dependencies with semicolon inside, bu

RE: Need a target meta data for parallel executor.

Alexey, Can you describe a little how this parallel executor works? How do you specify things that can run in parallel and those that need to run sequentially due to dependencies. One thing I wanted in along past was to allow specifying in the dependencies something like: depends="a,b,c;d,f,g;

Re: Need a target meta data for parallel executor.

This will work right now (and I did put semicolon in the property value to define several sets). It just seems inconvenient. - Alexey. Matt Benson wrote: Doesn't the possibility exist that different sets of mutex targets would exist? So you could have: And ParallelExecutor would know to use a

Re: Need a target meta data for parallel executor.

Doesn't the possibility exist that different sets of mutex targets would exist? So you could have: And ParallelExecutor would know to use a PropertySet looking for ParallelExecutor.mutex. as the properties' prefix. I get a headache thinking where to go from there. ;) -Matt --- "Alexey N. S

Re: Purpose of FileUtils.close(...)

I have lost the original thread, but anyway, those who participated in the discussion should remember it. In talking about whether caught Exceptions should at least be logged, Jesse mentioned "disk full" as an example. We actually have a bugrep (32676) about full directories, and I found a blog t

Re: Need a target meta data for parallel executor.

I meant "What do you propose..." stupid computer did not see the problem... Alexey N. Solofnenko wrote: So, would do you propose? Is it something like: The target mutual exclusion seems static and nobody should be changing it from an outside (only build script developer should know about the

Re: Need a target meta data for parallel executor.

So, would do you propose? Is it something like: The target mutual exclusion seems static and nobody should be changing it from an outside (only build script developer should know about them). On the other hand adding even more ANT constructs for every small detail seems an overkill. If we a

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

mbenson 2005/01/19 10:34:48 Modified:src/main/org/apache/tools/ant/types Tag: ANT_16_BRANCH PropertySet.java Log: Sync to HEAD Revision ChangesPath No revision No revision 1.8.2.10 +31 -32ant/src/main/or

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

mbenson 2005/01/19 10:33:09 Modified:src/main/org/apache/tools/ant/types PropertySet.java Log: Javadoc Revision ChangesPath 1.23 +31 -32ant/src/main/org/apache/tools/ant/types/PropertySet.java Index: PropertySet.java ===

Re: Need a target meta data for parallel executor.

Alexey: Since the Executor classname itself is specified as an option, rather than in a buildfile, my opinion would be that specifications that interact with an Executor should be externally configurable. At the same time it would be nice to maintain Target exclusivity information with the target

Need a target meta data for parallel executor.

Hello, I am experimenting with parallel executor. One of the things required for it is to be able to prevent some targets (mostly test targets) to be executed simultaneously. It is possible to add something like "mutex-names" attribute to Target, but if we do that, there seems no end of addin

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

mbenson 2005/01/19 09:15:10 Modified:src/main/org/apache/tools/ant/util Tag: ANT_16_BRANCH LazyFileOutputStream.java Log: Merge Revision ChangesPath No revision No revision 1.1.2.5 +4 -2 ant/src/main/

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

mbenson 2005/01/19 09:14:01 Modified:src/main/org/apache/tools/ant/util LazyFileOutputStream.java Log: Minor javadoc. Revision ChangesPath 1.7 +4 -2 ant/src/main/org/apache/tools/ant/util/LazyFileOutputStream.java Index: LazyFileOutputStream.java ==

[GUMP@brutus]: Project test-ant (in module ant) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project test-ant has an issue affecting its community integration. This issue affects 1 p

DO NOT REPLY [Bug 33162] New: - OutOfMemoryException when compiling a large project

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