1. 04 Dec, 2017 1 commit
  2. 30 Nov, 2017 1 commit
  3. 27 Nov, 2017 3 commits
  4. 25 Nov, 2017 1 commit
  5. 23 Nov, 2017 8 commits
  6. 22 Nov, 2017 9 commits
  7. 21 Nov, 2017 9 commits
  8. 20 Nov, 2017 3 commits
    • Kevin Funk's avatar
      test_kdevformatsource: Fix crash on Windows · 0e43fa96
      Kevin Funk authored
      Unit test is still not fixed though.
      22:30:32 FAIL!  : KDevelop::TestKdevFormatSource::testNoCommands()
      Compared values are not the same
      22:30:32    Actual   (initTest(formatFileData)): 0
      22:30:32    Expected (true)                    : 1
      22:30:32 C:\CI\workspace\KDevelop kdevelop stable-kf5-qt5
      WindowsMSVCQt5.9\kdevplatform\util\tests\test_kdevformatsource.cpp(53) :
      failure location
      22:30:32 QFATAL : KDevelop::TestKdevFormatSource::testNoCommands()
      ASSERT failure in QTest::fetchData(): "Test data requested, but no
      testdata available.", file
      line 1105
    • Kevin Funk's avatar
      Fix crash deep inside VcsOverlayProxyModel::data() · 6d4591fb
      Kevin Funk authored
      VcsOverlayProxyModel::data() calls ProjectController::changesModel()
      which currently is a non-const method which might create an instance
      of ProjectChangesModel which in turn triggers some KJobs.
      Avoid that by instantiating ProjectChangesModel() immediately during
      startup. I don't think that has a real performance impact.
      BUG: 384162
      FIXED-IN: 5.2.1
      Reviewers: apol
      Reviewed By: apol
      Subscribers: mwolff, dfaure, brauch, apol, kdevelop-devel
      Differential Revision: https://phabricator.kde.org/D8852
    • Sven Brauch's avatar
      compute itemrepository version from version plus KDEVELOP_VERSION · 53ec893e
      Sven Brauch authored
      This ensures that for each release, we clear the item repository.
      In the past, we had various issues related to old caches -- this change
      should avold that, since we no longer need to remember to bump the
      ITEMREPOSITORY_VERSION variable on each release.
      Changing ITEMREPOSITORY_VERSION is still possible to force a clear even
      if KDEVELOP_VERSION is untouched.
  9. 19 Nov, 2017 1 commit
    • Milian Wolff's avatar
      Don't add the same targets multiple times for nested CMake projects · c2f9b5f2
      Milian Wolff authored
      When we import a cmake project folder and that contains nested
      CMake projects, we ended up showing the same target multiple times,
      since the CMake server output will reference the same targets for
      the parent project and then again for the nested project(s).
      Ensure the targets are only added once to fix this issue.
      BUG: 387095
  10. 18 Nov, 2017 2 commits
    • Friedrich W. H. Kossebau's avatar
    • Milian Wolff's avatar
      kdev-clang: Offer all include paths for code completion · 015141e3
      Milian Wolff authored
      We used to only offer code completion of project paths for local
      code completion in `#include "..."` contexts. And for vice versa,
      we only offered system paths for global code completion in
      `#include <...>` contexts. This is wrong, as the include style
      only changes the order in which a compiler iterates through these
      paths to find an include file. For code completion purposes, this
      is not important.
      Now we offer code completion in both path lists always. To show the
      user the right file/dir being included, we don't sort and unify the
      search path list anymore as that potentially changes the final result.
      Rather, we use a hash set to ensure we don't encounter paths multiple
      times and iterate over the search path lists in their original order.
      BUG: 386421
  11. 17 Nov, 2017 2 commits