Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of ndimiduk@gmail.com designates
 209.85.214.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALte62zytWz0uADRX8JiutHV8FLPZiwvb-oAXQ5TRQqrMOdJ_A@mail.gmail.com>
References: 
 <CAAg3a2pOMmYNr8nEgkkMskPF5rZ4OwfMCYBav4Lf1hBuHeWKSQ@mail.gmail.com>
 <CAPQV63Xtm7rPu+soPDAse99KWhR2Z_JXV+3XA2Lm-F3Bbw4Aqw@mail.gmail.com>
 <CAAg3a2r5p5_s7HYvqzXvDB=TWoKeuyfb5vYs1-xgmrtomqCNTA@mail.gmail.com>
 <CA+RK=_DOddi9FFHXjBUVnpxsJzvkocdmHE_2L==++2mixPHBbw@mail.gmail.com>
 <CAAg3a2o-W86cYqgv6-MZQA=1in0O5S_d-r9ij684zFOj_Om7pw@mail.gmail.com>
 <CA+RK=_AsVMqYduy_dBTJ+Tbpm1A4h9WnHM9qpp+fpt4MjjwYsw@mail.gmail.com>
 <CALPvCiCa_avJzDKzxb6N8tTPj1EbZPqRuc=mja50TKNQG81F0w@mail.gmail.com>
 <CAPQV63W8p4S4xbmebEbDiBP+2pztXnpnc6mzukoiiyxbpAUKqQ@mail.gmail.com>
 <CANZa=GsE-GhSNsxL11jVjpbOC_N6D6czTBKsYsrzkAqKyjvspw@mail.gmail.com>
 <CALte62zytWz0uADRX8JiutHV8FLPZiwvb-oAXQ5TRQqrMOdJ_A@mail.gmail.com>
From: Nick Dimiduk <ndimiduk@gmail.com>
Date: Wed, 20 Aug 2014 12:28:22 -0700
Message-ID: 
 <CANZa=GuTZ271Ax3kedAMyDifmcpn0yETzTg-r4k56GwUrypWwA@mail.gmail.com>
Subject: Re: 0.98-trunk build (pom) issue
To: hbase-dev <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11c1fe1e9e9c800501149ccb

--001a11c1fe1e9e9c800501149ccb
Content-Type: text/plain; charset=UTF-8

On Wed, Aug 20, 2014 at 12:12 PM, Ted Yu <yuzhihong@gmail.com> wrote:

> Minor correction: -Dhadoop-two.version=2.3.0 should be used.
>

Ha! Good catch Ted.

 On Wed, Aug 20, 2014 at 12:07 PM, Nick Dimiduk <ndimiduk@gmail.com> wrote:
>
> > The hadoop related profiles are for major versions (in branch-1 and
> > master). We have "hadoop-2.0" (current default) and "hadoop-3.0" (enabled
> > by specifying -Dhadoop.profile=3.0). I don't know why profiles are
> enabled
> > via property instead of by specifying the property (-P). These profiles
> > specify which hbase modules and dependency artifact (not version) should
> be
> > used.
> >
> > The exact hadoop version is specified by a separate property. The
> > hadoop-2.0 profile check the property "hadoop-two.version". The
> hadoop-3.0
> > profile appears to use "hadoop.version" property.
> >
> > So to build branch-1 vs hadoop-2.3.0, you would use "mvn
> > -Phadoop-two.version=2.3.0".
> >
> > At least, that's what it looks like by reading the pom. Any patches to
> > clean these parts of the build are welcome ;)
> >
> > -n
> >
> >
> > On Wed, Aug 20, 2014 at 11:55 AM, Jean-Marc Spaggiari <
> > jean-marc@spaggiari.org> wrote:
> >
> > > " don't specify hadoop.profile unless != 2.0."
> > >
> > > So if we build against 2.3.0 should we specify -Phadoop.profile=2.3 ?
> Or
> > we
> > > don't specify unless != 2.x?
> > >
> > > Thanks,
> > >
> > > JM
> > >
> > >
> > > 2014-08-14 14:03 GMT-04:00 Esteban Gutierrez <esteban@cloudera.com>:
> > >
> > > > What Andrew said. I'm building against 2.3.0 without any issue so
> far.
> > > >
> > > > cheers,
> > > > esteban.
> > > >
> > > >
> > > > --
> > > > Cloudera, Inc.
> > > >
> > > >
> > > >
> > > > On Thu, Aug 14, 2014 at 10:58 AM, Andrew Purtell <
> apurtell@apache.org>
> > > > wrote:
> > > >
> > > > > Oh. Sorry. Just remembered... to select the default profile you
> don't
> > > > > specify hadoop.profile. -Phadoop.profile=2.0 will cause issues,
> yes,
> > > > don't
> > > > > specify hadoop.profile unless != 2.0. And IIRC specifying a
> specific
> > > > Hadoop
> > > > > 2 version requires:
> > > > >
> > > > > -Dhadoop.version=2.x.x -Dhadoop-two.version=2.x.x
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Aug 14, 2014 at 10:51 AM, Vladimir Rodionov <
> > > > > vladrodionov@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > -Phadoop.version=2.2 worked fine to me. I was able to build
> package
> > > and
> > > > > > create eclipse workspace. I just checked dependencies and all
> > hadoop
> > > > libs
> > > > > > are 2.2?
> > > > > >
> > > > > > -Vladimir Rodionov
> > > > > >
> > > > > >
> > > > > > On Thu, Aug 14, 2014 at 10:37 AM, Andrew Purtell <
> > > apurtell@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > There is no hadoop.profile named "2.2". Use "2.0"
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Aug 14, 2014 at 10:34 AM, Vladimir Rodionov <
> > > > > > > vladrodionov@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Actually, -Phadoop.profile=2.2.
> > > > > > > >
> > > > > > > > -Vladimir Rodionov
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, Aug 14, 2014 at 10:28 AM, Jean-Marc Spaggiari <
> > > > > > > > jean-marc@spaggiari.org> wrote:
> > > > > > > >
> > > > > > > > > You should try mvn clean package -DskipTests
> > > -Dhadoop.profile=2.0
> > > > > > > > >
> > > > > > > > > JM
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > 2014-08-14 13:27 GMT-04:00 Vladimir Rodionov <
> > > > > vladrodionov@gmail.com
> > > > > > >:
> > > > > > > > >
> > > > > > > > > > I just synced my local 0.98-trunk and tried to build it:
> > > > > > > > > >
> > > > > > > > > > mvn clean package -DskipTests -Dhadoop.profile=2.2
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > [INFO] Scanning for projects...
> > > > > > > > > > [ERROR] The build could not read 1 project -> [Help 1]
> > > > > > > > > > [ERROR]
> > > > > > > > > > [ERROR]   The project
> > org.apache.hbase:hbase:0.98.6-SNAPSHOT
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> (/Users/vrodionov/Development/hbase/vanila/hbase-0.98-trunk-patch-new/pom.xml)
> > > > > > > > > > has 2 errors
> > > > > > > > > > [ERROR]
> > > > > > 'dependencyManagement.dependencies.dependency.artifactId'
> > > > > > > > for
> > > > > > > > > > org.apache.hbase:${compat.module}:jar with value
> > > > > '${compat.module}'
> > > > > > > > does
> > > > > > > > > > not match a valid id pattern. @ line 997, column 21
> > > > > > > > > > [ERROR]
> > > > > > 'dependencyManagement.dependencies.dependency.artifactId'
> > > > > > > > for
> > > > > > > > > > org.apache.hbase:${compat.module}:test-jar with value
> > > > > > > > '${compat.module}'
> > > > > > > > > > does not match a valid id pattern. @ line 1002, column 21
> > > > > > > > > > [ERROR]
> > > > > > > > > > [ERROR] To see the full stack trace of the errors, re-run
> > > Maven
> > > > > > with
> > > > > > > > the
> > > > > > > > > -e
> > > > > > > > > > switch.
> > > > > > > > > > [ERROR] Re-run Maven using the -X switch to enable full
> > debug
> > > > > > > logging.
> > > > > > > > > > [ERROR]
> > > > > > > > > > [ERROR] For more information about the errors and
> possible
> > > > > > solutions,
> > > > > > > > > > please read the following articles:
> > > > > > > > > > [ERROR] [Help 1]
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > -Vladimir Rodionov
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Best regards,
> > > > > > >
> > > > > > >    - Andy
> > > > > > >
> > > > > > > Problems worthy of attack prove their worth by hitting back. -
> > Piet
> > > > > Hein
> > > > > > > (via Tom White)
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
> > > > >
> > > > >    - Andy
> > > > >
> > > > > Problems worthy of attack prove their worth by hitting back. - Piet
> > > Hein
> > > > > (via Tom White)
> > > > >
> > > >
> > >
> >
>

--001a11c1fe1e9e9c800501149ccb--