v11.1.0

Thanks

• For reporting ConcurrentModificationException from Structure View
  • Binyomin Greenes (@Ben52)
  • Sparta Science (@sparta-developers)
  • Michael Chen (@QC15213)
  • wenfu.p (@feng19)
  • Domenico Visconti (@visd0m)
  • Yordis Prieto (@yordis)
  • Yuguang Zhang (@yuguang)
  • John Christopher (@jgchristopher)
  • Hoang Tran (@hoangtranwork)
  • Luigi Clemente (@Gigitsu)
  • Aaron Myatt (@aaronmyatt)
  • James Mitchell (@mezz)
  • Sean Washington (@seanwash)
  • Ross van Zyl (@rossvz)
  • Andrew Aunelle (@AndroidOatmeal)
  • Kurt Lenfesty (@kurtlenfesty)
  • Cesar (@cesarslzr)
• For reporting that the typeID could not be read from partial .beam files.
  • Manuel Méndez (@charangas)
  • Zbigniew Pękala (@zbigniewpekala)
  • Ilya Gorskin (@Revent)
  • Carlos Brito Lage (@cblage)
  • Kevin Hagel (@kevinhagel)
  • Eugene (@virtual-light)
  • Steve Ops (@steveops)
  • @fahadnaeemkhan
  • Raz (@RazgrizHsu)
  • Marvin Lee Fimmel (@Ekranos)
  • @fahadnaeemkhan
  • Dmitrii Golub (@Houdini)
  • Nick Bauman (@nickbauman)
  • Eric des Courtis (@edescourtis)

Changelog

v11.1.0

Enhancements

• #1587 - @KronicDeth
  • Update gradle plugins
    • gradle-intellij-plugin (org.jetbrains.intellij) to 0.4.10
    • org.jetbrains.kotlin.jvm to 1.3.50
    • de.undercrouch.download to 4.0.0
  • Update IDEA version in builds
    • 2019.2 -> 2019.2.2

Bug Fixes

• #1582 - @KronicDeth
  • Don't log if partial or no header typeID is read. It happens too often due to .beam files being written partially to disk during the build process. They will be re-indexed when they are complete.
• #1587 - @KronicDeth
  • Update gradle intellij plugin to fix runIde on newer macOS.
• #1588 - @KronicDeth

  • Fix ConcurrentModificationException in Structure View

    Java 9 fixed a bug (https://bugs.openjdk.java.net/browse/JDK-8071667) in HashMap where computeIfAbsent did not check for concurrent modifications, and it turns out that TreeElementList was using concurrent modifications, so it was now broke.

    Fixed by use get or put if it is absent, so that putNew can ensure that the CallDefinition is in the TreeElementList before it is added to the MutableList<TreeElement>, which was the original reason why there was a put inside of computeIfAbsent, which would have put when the function returned anyway.