On Mon, Dec 23, 2013 at 2:36 AM, ramkrishna vasudevan <
[email protected]> 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
