[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509980#comment-15509980
]
David Portabella commented on HBASE-15925:
--
I see that two new versions are published in maven central (1.2.2 and 1.2.3),
that's great!
one question:
this version 1.2.1 (and all previous versions) had this direct dependency's
artifactId on ${compat.module}, and we could see this here:
http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1
however, I don't see this anymore. why?
Does this mean that you have fixed and replaced the 1.2.1 version (and all the
previous ones)?
If so, isn't that incorrect? a release version should stay immutable forever.
Compiling a code which depends on a release dependency should always produce
the same result.
Or maybe mvnrepository.com now resolves these variables, and it was not the
case when this ticket was open?
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371187#comment-15371187
]
David Portabella commented on HBASE-15925:
--
Sean, I've filled a bug report at sbt based on your answer. could you please
check it?
https://github.com/sbt/sbt/issues/2666
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368584#comment-15368584
]
David Portabella commented on HBASE-15925:
--
Ok, yes, it works :)
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368327#comment-15368327
]
David Portabella commented on HBASE-15925:
--
{quote}
David Portabella can you verify 1.2.2rc2 specifically with it's repository:
https://repository.apache.org/content/repositories/orgapachehbase-1142/
{quote}
I try as follows:
{code}
$ git clone https://github.com/dportabella/spark-examples.git
# edit build.sbt:
replace: val hbaseVersion = "1.2.2rc2"
add: resolvers += "Apache Staging" at
"https://repository.apache.org/content/repositories/orgapachehbase-1142/;
$ rm -Rf /david/.ivy2/cache/org.apache.hbase
$ rm -Rf /david/.m2/repository/org/apache/hbase/
$ sbt run
{code}
result:
{code}
[info] Resolving org.apache.hbase#hbase-testing-util;1.2.2rc2 ...
[warn] module not found: org.apache.hbase#hbase-testing-util;1.2.2rc2
[warn]
https://repository.apache.org/content/repositories/orgapachehbase-1142/org/apache/hbase/hbase-testing-util/1.2.2rc2/hbase-testing-util-1.2.2rc2.pom
{code}
it does not find 1.2.2rc2. am i doing sthy wrong?
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367983#comment-15367983
]
David Portabella commented on HBASE-15925:
--
oh, i understand now.
thanks for the explanation. :)
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367936#comment-15367936
]
David Portabella commented on HBASE-15925:
--
{quote}
> So, I don't know why maven does not complain on 1.2.1 (see my post above),
> but sbt complains on 1.2.1 and now it works on 1.2.2.
> So, I guess the problem is solved. Thanks!
Glad to hear sbt now works! Maven should work correctly both before and after
this patch (before only so long as it's a version that correctly handles
default profiles, which should be all of the maven 3s).
{quote}
I am not sure that you understood what I mean. I will rephrase it:
hbase-testing-util version 1.2.1 has a problem, that has a dependency with a
variable not evaluated (it's the point of this ticket actually)
http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1
so, a maven pom.xml which declares a dependency on hbase-testing-util version
1.2.1 should fail, as it cannot download all of its dependencies.
however, maven does not fail (and it should) as I mentioned in a this post
above. so, maybe there is a bug on maven.
https://issues.apache.org/jira/browse/HBASE-15925?focusedCommentId=15367707=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15367707
on the other hand, sbt complains if a project depends on hbase-testing-util
version 1.2.1, as it should.
and, sbt succeeds if a project depends on hbase-testing-util version 1.2.2,
meaning that this ticket has fixed the problem on hbase.
so, in this sense, there is possibly a bug on maven, not on sbt.
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367785#comment-15367785
]
David Portabella edited comment on HBASE-15925 at 7/8/16 2:59 PM:
--
I first reported the problem when running a scala code that depends on hbase
version "0.98.7-hadoop2".
Updating this code to use hbase version 1.2.1 (or anything from 1.x to 1.21)
fails with:
{code}
Unresolved dependencies path: org.apache.hbase:${compat.module}:1.2.1
{code}
it works now using hbase version 1.2.2.
if you want to try:
{code}
$ git clone https://github.com/dportabella/spark-examples.git
# edit build.sbt:
replace: val hbaseVersion = "1.2.2"
add: resolvers += "Apache Staging" at
"https://repository.apache.org/content/groups/staging/;
$ rm -Rf /Users/david/.ivy2//cache/org.apache.hbase
$ rm -Rf /Users/david/.m2//repository/org/apache/hbase/
$ sbt run
{code}
So, I don't know why maven does not complain on 1.2.1 (see my post above),
but sbt complains on 1.2.1 and now it works on 1.2.2.
So, I guess the problem is solved. Thanks!
was (Author: dportabella):
I first reported the problem when running a scala code that depends on hbase
version "0.98.7-hadoop2".
Updating this code to use hbase version 1.2.1 (or anything from 1.x to 1.21)
fails with:
{code}
Unresolved dependencies path: org.apache.hbase:${compat.module}:1.2.1
{code}
it works now using hbase version 1.2.2.
if you want to try:
{code}
$ git clone https://github.com/dportabella/spark-examples.git
# edit build.sbt:
replace: val hbaseVersion = "1.2.2"
add: resolvers += "Apache Staging" at
"https://repository.apache.org/content/groups/staging/;
$ sbt run
{code}
So, I don't know why maven does not complain on 1.2.1 (see my post above),
but sbt complains on 1.2.1 and now it works on 1.2.2.
So, I guess the problem is solved. Thanks!
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367785#comment-15367785
]
David Portabella edited comment on HBASE-15925 at 7/8/16 2:59 PM:
--
I first reported the problem when running a scala code that depends on hbase
version "0.98.7-hadoop2".
Updating this code to use hbase version 1.2.1 (or anything from 1.x to 1.21)
fails with:
{code}
Unresolved dependencies path: org.apache.hbase:${compat.module}:1.2.1
{code}
it works now using hbase version 1.2.2.
if you want to try:
{code}
$ git clone https://github.com/dportabella/spark-examples.git
# edit build.sbt:
replace: val hbaseVersion = "1.2.2"
add: resolvers += "Apache Staging" at
"https://repository.apache.org/content/groups/staging/;
$ rm -Rf /david/.ivy2//cache/org.apache.hbase
$ rm -Rf /david/.m2//repository/org/apache/hbase/
$ sbt run
{code}
So, I don't know why maven does not complain on 1.2.1 (see my post above),
but sbt complains on 1.2.1 and now it works on 1.2.2.
So, I guess the problem is solved. Thanks!
was (Author: dportabella):
I first reported the problem when running a scala code that depends on hbase
version "0.98.7-hadoop2".
Updating this code to use hbase version 1.2.1 (or anything from 1.x to 1.21)
fails with:
{code}
Unresolved dependencies path: org.apache.hbase:${compat.module}:1.2.1
{code}
it works now using hbase version 1.2.2.
if you want to try:
{code}
$ git clone https://github.com/dportabella/spark-examples.git
# edit build.sbt:
replace: val hbaseVersion = "1.2.2"
add: resolvers += "Apache Staging" at
"https://repository.apache.org/content/groups/staging/;
$ rm -Rf /Users/david/.ivy2//cache/org.apache.hbase
$ rm -Rf /Users/david/.m2//repository/org/apache/hbase/
$ sbt run
{code}
So, I don't know why maven does not complain on 1.2.1 (see my post above),
but sbt complains on 1.2.1 and now it works on 1.2.2.
So, I guess the problem is solved. Thanks!
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367785#comment-15367785
]
David Portabella commented on HBASE-15925:
--
I first reported the problem when running a scala code that depends on hbase
version "0.98.7-hadoop2".
Updating this code to use hbase version 1.2.1 (or anything from 1.x to 1.21)
fails with:
{code}
Unresolved dependencies path: org.apache.hbase:${compat.module}:1.2.1
{code}
it works now using hbase version 1.2.2.
if you want to try:
{code}
$ git clone https://github.com/dportabella/spark-examples.git
# edit build.sbt:
replace: val hbaseVersion = "1.2.2"
add: resolvers += "Apache Staging" at
"https://repository.apache.org/content/groups/staging/;
$ sbt run
{code}
So, I don't know why maven does not complain on 1.2.1 (see my post above),
but sbt complains on 1.2.1 and now it works on 1.2.2.
So, I guess the problem is solved. Thanks!
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367707#comment-15367707
]
David Portabella commented on HBASE-15925:
--
I no longer understand.
I've tried with 1.2.2 and it works, but now it also works on 1.2.1 from maven
central.
I've tried as follows:
{code}
$ mvn archetype:generate -DgroupId=com.example -DartifactId=App
-DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=true
{code}
I've added the hbase-testing-util 1.2.2 dependency and the
https://repository.apache.org/content/groups/staging/ repository.
pom.xml
{code}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0
com.example
App
jar
1.0-SNAPSHOT
App
http://maven.apache.org
junit
junit
3.8.1
test
org.apache.hbase
hbase-testing-util
1.2.2
apache_stage
Apache Stage
https://repository.apache.org/content/groups/staging/
{code}
And run:
{code}
$ rm -Rf /david/.m2/repository/org/apache/hbase/
$ mvn clean
$ mvn package
$ mvn exec:java -Dexec.mainClass="com.example.App"
{code}
and it works.
however, removing the repository and using 1.2.1 works also now.
I am investigating.
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366113#comment-15366113
]
David Portabella commented on HBASE-15925:
--
has 1.2.2 been published?
otherwise, is there something I can do to help make it happen?
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15925) compat-module maven variable not evaluated
[
https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15326317#comment-15326317
]
David Portabella commented on HBASE-15925:
--
thanks for fixing the issue.
when will 1.2.2 be published in maven central?
http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util
> compat-module maven variable not evaluated
> --
>
> Key: HBASE-15925
> URL: https://issues.apache.org/jira/browse/HBASE-15925
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.0.3, 1.1.5
>Reporter: Nick Dimiduk
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15925.1.patch
>
>
> Looks like we've regressed on HBASE-8488. Have a look at the dependency
> artifacts list on
> http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1.
> Notice the direct dependency's artifactId is {{$\{compat.module\}}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-8488) HBase transitive dependencies not being pulled in when building apps like Flume which depend on HBase
[
https://issues.apache.org/jira/browse/HBASE-8488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307889#comment-15307889
]
David Portabella commented on HBASE-8488:
-
This issue is not fixed yet.
All versions from 0.99.0 to the latest 1.2.1 of hbase-testing-util still depend
on the unresolved dependency org.apache.hbase ${compat.module}.
All versions from 0.96.0-hadoop1 to 0.98.19-hadoop2 work fine.
See here:
http://mvnrepository.com/artifact/org.apache.hbase/hbase-testing-util/1.2.1
> HBase transitive dependencies not being pulled in when building apps like
> Flume which depend on HBase
> -
>
> Key: HBASE-8488
> URL: https://issues.apache.org/jira/browse/HBASE-8488
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 0.95.0
>Reporter: Roshan Naik
>Assignee: stack
>Priority: Blocker
> Fix For: 0.98.0, 0.95.2
>
> Attachments: client.tgz
>
>
> Here is a snippet of the errors seen when building against Hbase
> {code}
> [WARNING] Invalid POM for org.apache.hbase:hbase-common:jar:0.97.0-SNAPSHOT,
> transitive dependencies (if any) will not be available, enable debug logging
> for more details: Some problems were encountered while processing the POMs:
> [ERROR] 'dependencyManagement.dependencies.dependency.artifactId' for
> org.apache.hbase:${compat.module}:jar with value '${compat.module}' does not
> match a valid id pattern. @ org.apache.hbase:hbase:0.97.0-SNAPSHOT,
> /Users/rnaik/.m2/repository/org/apache/hbase/hbase/0.97.0-SNAPSHOT/hbase-0.97.0-SNAPSHOT.pom,
> line 982, 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. @ org.apache.hbase:hbase:0.97.0-SNAPSHOT,
> /Users/rnaik/.m2/repository/org/apache/hbase/hbase/0.97.0-SNAPSHOT/hbase-0.97.0-SNAPSHOT.pom,
> line 987, column 21
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
