[
https://issues.apache.org/jira/browse/PIG-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890603#action_12890603
]
Dmitriy V. Ryaboy commented on PIG-1500:
----------------------------------------
Have you tried actually building with this? The reason I put guava r3 into lib
was that the public maven deploy for it is broken.
Here's what happens when I apply this patch and try to build:
{code}
[ivy:resolve] :::: WARNINGS
[ivy:resolve] problem while downloading module descriptor:
http://repo1.maven.org/maven2/com/google/guava/guava/r03/guava-r03.pom: invalid
sha1: expected=1cbd6fab2460050ff7147b6d8536f39c8f535067
computed=7a37041386ee39a1fbb3efd3c4c6932809cb5887 (1304ms)
{code}
Now, we can probably still get away with removing guava from lib/ -- they just
release guava-r6, which should be compatible with the guava-dependent code in
Pig, and is supposed to have a proper maven deploy. But the patch as is should
not be applied.
> guava.jar should be removed from the lib folder
> -----------------------------------------------
>
> Key: PIG-1500
> URL: https://issues.apache.org/jira/browse/PIG-1500
> Project: Pig
> Issue Type: Bug
> Components: build
> Reporter: Giridharan Kesavan
> Assignee: niraj rai
> Fix For: 0.8.0
>
> Attachments: removeGuavaJar.patch
>
>
> guava jar is available in the maven repository but still its is checked into
> the pig trunk's lib folder.
> I ve checked the availability of guava jar in the maven repository.
> http://mvnrepository.com/artifact/com.google.guava/guava
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
