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:

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

Reply via email to