Wouldn't adding 23 to version mess with resolution rules?

On Feb 22, 2012, at 6:01 PM, "Daniel Dai (Commented) (JIRA)" <[EMAIL PROTECTED]> wrote:

>
>    [ https://issues.apache.org/jira/browse/PIG-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214111#comment-13214111 ]
>
> Daniel Dai commented on PIG-2546:
> ---------------------------------
>
> Yes, we shall change build.xml to have a different name for 23 artifacts. That's it.
>
>> build and publish Pig artifacts compiled against Hadoop 0.23
>> ------------------------------------------------------------
>>
>>                Key: PIG-2546
>>                URL: https://issues.apache.org/jira/browse/PIG-2546
>>            Project: Pig
>>         Issue Type: Task
>>         Components: build
>>   Affects Versions: 0.9.2
>>           Reporter: Alejandro Abdelnur
>>           Priority: Critical
>>            Fix For: 0.9.2
>>
>>
>> The pig JAR available in Apache Maven repo has been compiled with a version of Hadoop prior to 0.23.
>> This JAR cannot be used to run Pig against Hadoop 0.23 because of changes in the JobControl API [ie the JobControl.addJob(Job) method now is JobControl.addJob(ControlledJob), and while Job implements ControlledJob, because ControlledJob is an interface, the generated bytecode for the signature is different).
>> I assume we'll need 2 different versions of the JARs, one for pre 0.23 and one for post 0.23.
>> This affects Oozie integration with Hadoop 0.23
>
> --
> 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
>
>

I was chatting with abayer and he suggest we should use a classifier for
one of the JARs

So JARs would be something like this:

pig-0.9.2.jar
pig-0.9.2-h0.23.jar (h0.23 classifier)

Then version resolution rules would work.

And when consuming a PIG JAR, the classifier should be specified when using
0.23

Thanks.

Alejandro

On Wed, Feb 22, 2012 at 4:06 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:

> Wouldn't adding 23 to version mess with resolution rules?
>
> On Feb 22, 2012, at 6:01 PM, "Daniel Dai (Commented) (JIRA)" <
> [EMAIL PROTECTED]> wrote:
>
> >
> >    [
> https://issues.apache.org/jira/browse/PIG-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214111#comment-13214111]
> >
> > Daniel Dai commented on PIG-2546:
> > ---------------------------------
> >
> > Yes, we shall change build.xml to have a different name for 23
> artifacts. That's it.
> >
> >> build and publish Pig artifacts compiled against Hadoop 0.23
> >> ------------------------------------------------------------
> >>
> >>                Key: PIG-2546
> >>                URL: https://issues.apache.org/jira/browse/PIG-2546
> >>            Project: Pig
> >>         Issue Type: Task
> >>         Components: build
> >>   Affects Versions: 0.9.2
> >>           Reporter: Alejandro Abdelnur
> >>           Priority: Critical
> >>            Fix For: 0.9.2
> >>
> >>
> >> The pig JAR available in Apache Maven repo has been compiled with a
> version of Hadoop prior to 0.23.
> >> This JAR cannot be used to run Pig against Hadoop 0.23 because of
> changes in the JobControl API [ie the JobControl.addJob(Job) method now is
> JobControl.addJob(ControlledJob), and while Job implements ControlledJob,
> because ControlledJob is an interface, the generated bytecode for the
> signature is different).
> >> I assume we'll need 2 different versions of the JARs, one for pre 0.23
> and one for post 0.23.
> >> This affects Oozie integration with Hadoop 0.23
> >
> > --
> > 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
> >
> >
>