hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8224) Add '-hadoop1' or '-hadoop2' to our version string
Date Wed, 31 Jul 2013 21:45:49 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725750#comment-13725750

stack commented on HBASE-8224:

[~ndimiduk] Short answer, yes.  Our published poms have uninterpreted variables and a selection
of profiles to choose defaulting to a hadoop1 if non-chosen.  Profiles are how you customize
your build.  We want to customize the customization.

[~brocknoland] Thanks boss.  Let me see if can make it so default profile matches the -hadoop1
or -hadoop2 ending.

[~enis] Yeah, that is the road I took last night using a script to generate pom.xml.hadoop1
and pom.xml.hadoop2 then building passing the particular pom w/ the -f flag.  Tricky parts
are the fact that modules refer to parent and they also need to run the custom pom, there
are lots of changes to make, and we are polluting our src tree.  Working on it.
> Add '-hadoop1' or '-hadoop2' to our version string
> --------------------------------------------------
>                 Key: HBASE-8224
>                 URL: https://issues.apache.org/jira/browse/HBASE-8224
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.95.2
>         Attachments: 8224-adding.classifiers.txt, hbase-8224-proto1.patch
> So we can publish both the hadoop1 and the hadoop2 jars to a maven repository, and so
we can publish two packages, one for hadoop1 and one for hadoop2, given how maven works, our
only alternative (to the best of my knowledge and after consulting others) is by amending
the version string to include hadoop1 or hadoop2.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message