You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by ramkrishna vasudevan <ra...@gmail.com> on 2013/12/23 11:36:06 UTC
Compiling with hadoop 2.0 and hadoop 3.0
Trying to execute
mvn clean install -DskipTests -Dhadoop.profile=2.0
mvn clean install -DskipTests -Dhadoop.profile=3.0
I get the following error
[ERROR] The project org.apache.hbase:hbase:0.99.0-SNAPSHOT
(/home/ram/hbase_test/trunk/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 1005, 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 1010, column 21
Running with
mvn clean install -DskipTests -Dhadoop.profile=1.0 and without
hadoop.profile makes it work.
Regards
Ram
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by Ted Yu <yu...@gmail.com>.
Ram:
Did you refer to compiling against hadoop 2.0 ?
I got same error when specifying -Dhadoop.profile=2.0
But this shouldn't be a blocker for you - hadoop2 is the default profile.
Cheers
On Mon, Dec 23, 2013 at 8:28 AM, ramkrishna vasudevan <
ramkrishna.s.vasudevan@gmail.com> wrote:
> Are you able to compile it Ted? I tried once again, am not able to compile
> it. May be i should clean the maven repo and again try.
>
>
>
> On Mon, Dec 23, 2013 at 7:36 PM, Ted Yu <yu...@gmail.com> wrote:
>
> > For compiling against Hadoop 3, there is HBASE-6581 which is in progress.
> >
> > Hadoop 2 is the default profile for trunk.
> >
> > Cheers
> >
> > On Dec 23, 2013, at 2:36 AM, ramkrishna vasudevan <
> > ramkrishna.s.vasudevan@gmail.com> wrote:
> >
> > > Trying to execute
> > > mvn clean install -DskipTests -Dhadoop.profile=2.0
> > > mvn clean install -DskipTests -Dhadoop.profile=3.0
> > > I get the following error
> > >
> > > [ERROR] The project org.apache.hbase:hbase:0.99.0-SNAPSHOT
> > > (/home/ram/hbase_test/trunk/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 1005, 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 1010, column 21
> > >
> > > Running with
> > > mvn clean install -DskipTests -Dhadoop.profile=1.0 and without
> > > hadoop.profile makes it work.
> > >
> > > Regards
> > > Ram
> >
>
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by ramkrishna vasudevan <ra...@gmail.com>.
Are you able to compile it Ted? I tried once again, am not able to compile
it. May be i should clean the maven repo and again try.
On Mon, Dec 23, 2013 at 7:36 PM, Ted Yu <yu...@gmail.com> wrote:
> For compiling against Hadoop 3, there is HBASE-6581 which is in progress.
>
> Hadoop 2 is the default profile for trunk.
>
> Cheers
>
> On Dec 23, 2013, at 2:36 AM, ramkrishna vasudevan <
> ramkrishna.s.vasudevan@gmail.com> wrote:
>
> > Trying to execute
> > mvn clean install -DskipTests -Dhadoop.profile=2.0
> > mvn clean install -DskipTests -Dhadoop.profile=3.0
> > I get the following error
> >
> > [ERROR] The project org.apache.hbase:hbase:0.99.0-SNAPSHOT
> > (/home/ram/hbase_test/trunk/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 1005, 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 1010, column 21
> >
> > Running with
> > mvn clean install -DskipTests -Dhadoop.profile=1.0 and without
> > hadoop.profile makes it work.
> >
> > Regards
> > Ram
>
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by Ted Yu <yu...@gmail.com>.
For compiling against Hadoop 3, there is HBASE-6581 which is in progress.
Hadoop 2 is the default profile for trunk.
Cheers
On Dec 23, 2013, at 2:36 AM, ramkrishna vasudevan <ra...@gmail.com> wrote:
> Trying to execute
> mvn clean install -DskipTests -Dhadoop.profile=2.0
> mvn clean install -DskipTests -Dhadoop.profile=3.0
> I get the following error
>
> [ERROR] The project org.apache.hbase:hbase:0.99.0-SNAPSHOT
> (/home/ram/hbase_test/trunk/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 1005, 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 1010, column 21
>
> Running with
> mvn clean install -DskipTests -Dhadoop.profile=1.0 and without
> hadoop.profile makes it work.
>
> Regards
> Ram
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by Jesse Yates <je...@gmail.com>.
Theoretically, it could also be used to specify an arbitrary hadoop
compilation target, but its always been so different (in terms of required
modules) that it never really could work out :-/
-------------------
Jesse Yates
@jesse_yates
jyates.github.com
On Mon, Dec 23, 2013 at 8:29 PM, ramkrishna vasudevan <
ramkrishna.s.vasudevan@gmail.com> wrote:
> Oh I see. So there was already an discussion on that. It was my ignorance.
> Sorry about that. Thanks for the replies.
>
>
> On Tue, Dec 24, 2013 at 8:58 AM, Stack <st...@duboce.net> wrote:
>
> > On Mon, Dec 23, 2013 at 3:10 PM, Nick Dimiduk <nd...@gmail.com>
> wrote:
> >
> > > Stack,
> > >
> > > Do you know why we use (-D) properties rather than using maven's
> > > -PprofileName to enable profiles? Maybe there's a discussion someplace
> > > where I can familiarize myself with this history?
> > >
> >
> > I believe it was our Nicolas Liochon that came up w/ this mechanism for
> > enabling profiles. I do not know the why.
> >
> > St.Ack
> >
>
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by ramkrishna vasudevan <ra...@gmail.com>.
Thanks Stack. I understand. In fact I spent some time to make it compile
with hadoop 2.0 thinking the compilation is failing due to some pom.xml
issues.
On Tue, Dec 24, 2013 at 1:08 PM, Stack <st...@duboce.net> wrote:
> On Mon, Dec 23, 2013 at 8:29 PM, ramkrishna vasudevan <
> ramkrishna.s.vasudevan@gmail.com> wrote:
>
> > Oh I see. So there was already an discussion on that. It was my
> ignorance.
> > Sorry about that. Thanks for the replies.
> >
> >
> This stuff is kinda cryptic. I updated the doc. but wouldn't have done so
> if you'd not brought it up.
> St.Ack
>
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by Stack <st...@duboce.net>.
On Mon, Dec 23, 2013 at 8:29 PM, ramkrishna vasudevan <
ramkrishna.s.vasudevan@gmail.com> wrote:
> Oh I see. So there was already an discussion on that. It was my ignorance.
> Sorry about that. Thanks for the replies.
>
>
This stuff is kinda cryptic. I updated the doc. but wouldn't have done so
if you'd not brought it up.
St.Ack
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by ramkrishna vasudevan <ra...@gmail.com>.
Oh I see. So there was already an discussion on that. It was my ignorance.
Sorry about that. Thanks for the replies.
On Tue, Dec 24, 2013 at 8:58 AM, Stack <st...@duboce.net> wrote:
> On Mon, Dec 23, 2013 at 3:10 PM, Nick Dimiduk <nd...@gmail.com> wrote:
>
> > Stack,
> >
> > Do you know why we use (-D) properties rather than using maven's
> > -PprofileName to enable profiles? Maybe there's a discussion someplace
> > where I can familiarize myself with this history?
> >
>
> I believe it was our Nicolas Liochon that came up w/ this mechanism for
> enabling profiles. I do not know the why.
>
> St.Ack
>
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by Stack <st...@duboce.net>.
On Mon, Dec 23, 2013 at 3:10 PM, Nick Dimiduk <nd...@gmail.com> wrote:
> Stack,
>
> Do you know why we use (-D) properties rather than using maven's
> -PprofileName to enable profiles? Maybe there's a discussion someplace
> where I can familiarize myself with this history?
>
I believe it was our Nicolas Liochon that came up w/ this mechanism for
enabling profiles. I do not know the why.
St.Ack
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by Nick Dimiduk <nd...@gmail.com>.
Stack,
Do you know why we use (-D) properties rather than using maven's
-PprofileName to enable profiles? Maybe there's a discussion someplace
where I can familiarize myself with this history?
Thanks,
Nick
On Mon, Dec 23, 2013 at 12:01 PM, Stack <st...@duboce.net> wrote:
> On Mon, Dec 23, 2013 at 2:36 AM, ramkrishna vasudevan <
> ramkrishna.s.vasudevan@gmail.com> wrote:
>
> > Trying to execute
> > mvn clean install -DskipTests -Dhadoop.profile=2.0
> > mvn clean install -DskipTests -Dhadoop.profile=3.0
> > I get the following error
> >
> > [ERROR] The project org.apache.hbase:hbase:0.99.0-SNAPSHOT
> > (/home/ram/hbase_test/trunk/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 1005, 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 1010, column 21
> >
> > Running with
> > mvn clean install -DskipTests -Dhadoop.profile=1.0 and without
> > hadoop.profile makes it work.
> >
>
>
> The technical term for what you are seeing above Ram, according to the
> issue that moved our default to hadoop2, is "maven bullshit": See
>
> https://issues.apache.org/jira/browse/HBASE-9955?focusedCommentId=13840761&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13840761
>
> You will get the above whenever you specify the default profile (Let me add
> a note to our doc).
>
> Maybe it is not a maven problem and rather a problem w/ the author of the
> above comment but IIRC, the author tried a few things to make it work and
> in the end just gave up on it.
>
> On the maven3 profile, our Eric Charles took a good stab at making it work;
> his patch just needs review/exercise, and if all good, commit (It may have
> gone a little stale by now -- my fault).
>
> St.Ack
>
Re: Compiling with hadoop 2.0 and hadoop 3.0
Posted by Stack <st...@duboce.net>.
On Mon, Dec 23, 2013 at 2:36 AM, ramkrishna vasudevan <
ramkrishna.s.vasudevan@gmail.com> wrote:
> Trying to execute
> mvn clean install -DskipTests -Dhadoop.profile=2.0
> mvn clean install -DskipTests -Dhadoop.profile=3.0
> I get the following error
>
> [ERROR] The project org.apache.hbase:hbase:0.99.0-SNAPSHOT
> (/home/ram/hbase_test/trunk/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 1005, 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 1010, column 21
>
> Running with
> mvn clean install -DskipTests -Dhadoop.profile=1.0 and without
> hadoop.profile makes it work.
>
The technical term for what you are seeing above Ram, according to the
issue that moved our default to hadoop2, is "maven bullshit": See
https://issues.apache.org/jira/browse/HBASE-9955?focusedCommentId=13840761&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13840761
You will get the above whenever you specify the default profile (Let me add
a note to our doc).
Maybe it is not a maven problem and rather a problem w/ the author of the
above comment but IIRC, the author tried a few things to make it work and
in the end just gave up on it.
On the maven3 profile, our Eric Charles took a good stab at making it work;
his patch just needs review/exercise, and if all good, commit (It may have
gone a little stale by now -- my fault).
St.Ack