[jira] [Resolved] (HBASE-15925) compat-module maven variable not evaluated

["Sean Busbey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey resolved HBASE-15925.
---------------------------------
    Resolution: Fixed

{quote}
I'm no longer convinced this can be confirmed with visual inspection. 
{quote}

Nope, can't be verified by looking because it's a matter of some tools treating Maven pom's incorrectly (most notably sbt). I'm not aware of any web tool that e.g. uses sbt to make a effective pom we could check.

{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!
{quote}

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).

I'll resolve this again now that we have things confirmed. Thanks for rechecking!

> 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)