[
https://issues.apache.org/jira/browse/HBASE-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108366#comment-13108366
]
Joep Rottinghuis commented on HBASE-4447:
-----------------------------------------
Just picked hbase.version to keep symmetric with avro.version, hadoop.version,
etc.
I see your point on project.version.
It's all the same to me. Which do you prefer?
Pls let me know before I crank out the patch for trunk.
Thanks,
Joep
-----Original Message-----
From: Jesse Yates [mailto:[email protected]]
Sent: Monday, September 19, 2011 9:26 PM
To: [email protected]
Subject: Re: Branching for 0.92 [WAS -> Re: [DISCUSSION] Accumulo, another
BigTable clone, has shown up on Apache Incubator as a proposal]
Yeah, that works too. Generally, I think people go with project.version, but it
doesn't really matter ;)
-Jesse
On Mon, Sep 19, 2011 at 9:22 PM, Rottinghuis, Joep <[email protected]>wrote:
> Just filed a jira with patch for this. See HBASE-4447.
>
> Thanks,
>
> Joep
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of
> Stack
> Sent: Monday, September 19, 2011 9:21 PM
> To: [email protected]
> Subject: Re: Branching for 0.92 [WAS -> Re: [DISCUSSION] Accumulo,
> another BigTable clone, has shown up on Apache Incubator as a
> proposal]
>
> On Mon, Sep 19, 2011 at 8:53 PM, Jesse Yates <[email protected]>
> wrote:
> > You should be able to pretty easily set in in the pom (under
> > properties), and then just use in the <version> tag.
> >
>
> Where are the pom properties Jesse?
> Thanks,
> St.Ack
> Allow hbase.version to be passed in as command-line argument
> ------------------------------------------------------------
>
> Key: HBASE-4447
> URL: https://issues.apache.org/jira/browse/HBASE-4447
> Project: HBase
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.92.0
> Reporter: Joep Rottinghuis
> Attachments: HBASE-4447-0.92.patch
>
>
> Currently the build always produces the jars and tarball according to the
> version baked into the POM.
> When we modify this to allow the version to be passed in as a command-line
> argument, it can still default to the same behavior, yet give the flexibility
> for an internal build to tag on own version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira