hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Groschupf (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-117) commons logging and log4j
Date Mon, 25 Feb 2008 19:38:51 GMT

    [ https://issues.apache.org/jira/browse/PIG-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572188#action_12572188
] 

Stefan Groschupf commented on PIG-117:
--------------------------------------

For now I suggest to have one pig-core jar and all dependencies cleanly listed or distributed
with it.
Sure we should have as less as possible dependencies. But my experience is that most users
are ok with a couple of jars in a lib folder as long they dont need to maintain those jars.
The user experience should be: 
Download zip file
extract file
start shell scrip
start using pig local
change some config values
use pig distributed.

As long getting started with pig is as easy as possible we can grow our user basis fast ==
more contributors == getting things stabile sooner.



> commons logging and log4j
> -------------------------
>
>                 Key: PIG-117
>                 URL: https://issues.apache.org/jira/browse/PIG-117
>             Project: Pig
>          Issue Type: Improvement
>            Reporter: Stefan Groschupf
>
> On the one hand side Pig uses commons logging - what makes sense. On the other hand side
the Pig Main class configure Log4j in the code. This introduce a log4j must have dependency.

> I suggest to only use a log4j configuration file to configure log4j and remove the log4j
configuration in the code. 
> Any thoughts?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message