[
https://issues.apache.org/jira/browse/PIG-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572910#action_12572910
]
Benjamin Francisoud commented on PIG-117:
-----------------------------------------
I like both suggestions (Alan's and Stefan's)
In my opinion, for pig first release, let's keep it simple and do what stefan
is suggesting (1 artifact and the lib jars)
When pig grows, pig may need to be split into different modules...
To do what Alan describe, using [Ivy|http://ant.apache.org/ivy/] would be the
perfect solution.
You would describe each pig artifact (pigserver, piggrunt etc...) and describe
each jar dependencies. Ivy will take care of the rest...
{code:xml}
<configurations>
<conf name="default" />
<conf name="server" extends="default" />
<conf name="grunt" extends="server" />
<conf name="test" extends="default" />
</configurations>
<publications>
<artifact name="pig-server" type="jar" ext="jar" conf="server" />
<artifact name="pig-grunt" type="jar" ext="jar" conf="grunt" />
</publications>
<dependencies>
<dependency org="commons-collections" name="commons-collections" rev="3.2"
conf="default"/>
<dependency org="junit" name="junit" rev="3.8.2" conf="test->default" />
<dependency org="log4j" name="log4j" rev="1.2.13" conf="test->grunt" />
...
<dependencies>
{code}
> 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.
