Re: [patch] javadoc, name-hiding, if/else nesting

if (condition) { return a; } return b; over: if (condition) { return a; } else { return b; } Only real benefit is to get rid of compiler warnings. I'm ambivalent about either way being "more correct", but the fewer warnings I get the better IMHO, so I remove nesting of returns in else

DO NOT REPLY [Bug 34424] New: - Version Update too low

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 34424] - Version Update too low

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 34425] New: - Manifest cause StringIndexOutOfBound error while processing multibyte characters

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 34425] - Manifest cause StringIndexOutOfBound error while processing multibyte characters

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 34424] - Version Update too low

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 1.6.3 release

Hello, I did not see yet any specific ant 1.6.3beta1 bugs. Can we already start discussing about a 1.6.3 release ? Or do we need a second beta ? I was thinking of proposing a release on Thursday, April 28th. Cheers, Antoine - To un

"Creating Manifest-Only Jar" message vanished in HEAD and 1.6.3beta1

Actually I did find a bug in 1.6.3.beta1 or a change of behavior. The message "Creating Manifest-Only Jar" which would happen when you are creating a jar but there happen not too be anything in the fileset(s) that you are jarring, vanished in 1.6.3beta1. I think it is due to a change which I did

[EMAIL PROTECTED]: Project dist-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 dist-ant has an issue affecting its community integration. This issue affects 19

java.lang.NullPointerException, launch.Locator.getLocationURLs

please help me if you can or have sorted already my same problem with ant. Following instructions on the installation manual, I do all things described in installation but not able to build ant since the build -Ddist.dir=3D ain_Ant_distribution> dist command has the following response: access den

Re: java.lang.NullPointerException, launch.Locator.getLocationURLs

Please don't cross-post to the user and dev lists. [EMAIL PROTECTED] wrote: please help me if you can or have sorted already my same problem with ant. Following instructions on the installation manual, I do all things described in installation but not able to build ant since the build -Ddist.dir=3D

RE: java.lang.NullPointerException, launch.Locator.getLocationURLs

I suggest you submit your question to the ant users group (appropriate forum) rather than the ant developers group (inappropriate forum). Also, you could search the ant users list archives to see if someone else had this same problem, and the group has already replied. -Original Message

Re: java.lang.NullPointerException, launch.Locator.getLocationURLs

It is a known problem. If the lib location is present but not accessible, ant will give this null pointer exception. There was some discussion on the dev list but I cannot remember if a fix went in. The "access denied" message implies that the "dist.dir" is not a good location to place the build.

Re: java.lang.NullPointerException, launch.Locator.getLocationURLs

>-- Messaggio Originale -- >Reply-To: "Ant Developers List" <[EMAIL PROTECTED]> >Date: Thu, 14 Apr 2005 00:13:56 +1000 >From: Conor MacNeill <[EMAIL PROTECTED]> >To: Ant Developers List <[EMAIL PROTECTED]> >Subject: Re: java.lang.NullPointerException, launch.Locator.getLocationURLs > > >Please do

Sorry to be off topic but

I (Steve) was a premature baby and am walking May 1st for medial research by march of dimes. I was hoping that You might be able to 1. Donate a few dollars 2. You could pass this message on to friends and family Donate at http://www.walkamerica.org/stevemorin http://www.walkameri

Re: junit test runner enhancements

Phil Weighill Smith wrote: Steve, I've not written any code to help here, but thought the following issue could also be considered: When executing a test class that has no test methods what-so-ever (e.g. someone comments out all tests for some reason) the runner currently barfs instead of ignoring