[
https://issues.apache.org/jira/browse/BIGTOP-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335363#comment-14335363
]
Konstantin Boudnik commented on BIGTOP-1589:
--------------------------------------------
bq. Cos, can you please provide more details about the compatibility mess you
are referring to?
I am talking about issues where code works with this version of Python and not
that version of it; libs getting changed, etc. I am no expert on that language,
mostly because of the horror stories I keep seeing on the inet and elsewhere.
I think you misread me - there's no strong reaction: just a question why it's a
good idea to introduce something they might be broken if target system has an
incompatible version of the environment? But let's take this discussion to the
new JIRA, I guess ;)
> 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)
