[ http://issues.apache.org/jira/browse/CONFIGURATION-232?page=all ]
Oliver Heger resolved CONFIGURATION-232.
----------------------------------------
Fix Version/s: Nightly Builds
Resolution: Fixed
The printStackTrace() statements have been removed and the log messages you
pointed out have been improved. Thank you for spotting this.
> ConfigurationUtils spews directly on std.err when exceptions
> ------------------------------------------------------------
>
> Key: CONFIGURATION-232
> URL: http://issues.apache.org/jira/browse/CONFIGURATION-232
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.3 Final
> Environment: n/a
> Reporter: Endre Stølsvik
> Assigned To: Oliver Heger
> Priority: Minor
> Fix For: Nightly Builds
>
>
> ConfigurationUtils:
> public static URL locate(String base, String name) {
> 3 x :
> catch ([Malformed|IO]URLException e) {
> e.printStackTrace();
> }
> }
> .. say no more.
> But while we're at it, the log-message (which, for some reason, actually goes
> to a logger, not uglily to the system) states "Configuration loaded from ..",
> which isn't true: The thing isn't loaded yet; it will be loaded. "Loading
> configuration from .." would be better, or maybe "Will be loading
> configuration from ..". In addition, these log-lines could state what was the
> "base", and in particular the case where it loads from "base path", the whole
> line reads wrong.
> For example: "Loading configuration ["+name+"] from base path ["+base+"].."
> and similar for the other lines.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
