You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2007/03/15 17:34:09 UTC
[jira] Closed: (CLI-128) Remove Commons-logging from CLI's pom.xml
[ https://issues.apache.org/jira/browse/CLI-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Yandell closed CLI-128.
-----------------------------
Resolution: Fixed
None of the three separate branches of CLI (1.x, 2.x and avalon) have logging in their project.xml or pom.xmls.
> Remove Commons-logging from CLI's pom.xml
> -----------------------------------------
>
> Key: CLI-128
> URL: https://issues.apache.org/jira/browse/CLI-128
> Project: Commons CLI
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: N/A
> Reporter: Andy Gerweck
> Priority: Minor
>
> A search of the code in commons-cli 1.0 shows that CLI (rightly) doesn't do any logging, but just raises exceptions when things go wrong. However, the pom.xml states that commons-logging is a dependency, which isn't true. Instead of making users manually exclude commons-logging, it should be removed from the pom.xml.
> I hope that future versions will continue to be free from logging, as it's completely unnecessary for such a simple and elegant library. There's just no reason that a simple argument parser should ever need to log its status, except perhaps while fixing a bug--but those statements would be unlikely to be useful again and are better removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org