[
https://issues.apache.org/jira/browse/JENA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201221#comment-13201221
]
Andy Seaborne commented on JENA-208:
------------------------------------
We can deal with this is the short term and the long term:
1/ Long term : a special module dedicated to producing the commands, including
log4j setup and a single jar file. JENA-190 (the value of a single jar file is
less with java6 because of lib/*).
2/ Short term: the scripts that run the commands include log4j settings.
3/ Short term: there is a log4j properties file not called "log4j properties"
that the commands all use if log4j setup not set externally.
> The command line applications need to set up log4j.
> ---------------------------------------------------
>
> Key: JENA-208
> URL: https://issues.apache.org/jira/browse/JENA-208
> Project: Jena
> Issue Type: Bug
> Reporter: Andy Seaborne
>
> Without a log4j setup, the command line tools will issue some warning
> messages.
> The commands should not do this - there needs to be a way to run command lien
> applications without other set up assumptions.
> See also JENA-36.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
