[
https://issues.apache.org/jira/browse/BIGTOP-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335278#comment-14335278
]
Mark Grover commented on BIGTOP-1589:
-------------------------------------
Thanks Sean. I will create a JIRA to re-write this.
Cos, can you please provide more details about the compatibility mess you are
referring to? At the end of the day, I think it's simply a language choice so I
don't want to elongate this argument and it seems to be a nice clean scripting
way of doing this. I don't see why a language choice would garner such a strong
reaction but perhaps there is something I am missing:-)
In any case, I will file a JIRA for the re-write.
> Prioritization is broken in bigtop-detect-javahome
> --------------------------------------------------
>
> Key: BIGTOP-1589
> URL: https://issues.apache.org/jira/browse/BIGTOP-1589
> Project: Bigtop
> Issue Type: Bug
> Components: general
> Affects Versions: 0.8.0
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments:
> 0001-BIGTOP-1589.-Prioritization-is-broken-in-bigtop-dete.patch,
> 0001-BIGTOP-1589.-Prioritization-is-broken-in-bigtop-dete.patch
>
>
> bigtop-detect-javahome uses 'ls -rd' to sort the JDKs in each category in
> reverse lexicographical order, but I believe when we switched to having
> separate variables defined for each major JDK version we overrode that
> mechanism so older JDKs still take precedence over newer ones.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
