Skip to main content
AgeCommit message (Collapse)AuthorFilesLines
2018-05-29Update license to EPL-2.0Matthias Sohn3-6/+12
Bug: 530393 Change-Id: Iea3b247253a97c28043187df0e35daecf518011e Signed-off-by: Matthias Sohn <>
2016-05-22Replace uses of deprecated Repository.getRef()Thomas Wolf1-2/+2
Use Repository.findRef() or Repository.exactRef(), as appropriate. No functional change. Change-Id: Ie481c7fa5ac69d4778cf9f70ac2b019bee6e53c9 Signed-off-by: Thomas Wolf <>
2016-05-03Test stability: avoid asynchronous SWTBotTreeItem.expand()Thomas Wolf3-13/+10
Sometimes tests do not find children of expanded tree nodes. The root cause appears to be that expand() expands the node in an asyncExec.[1] Add a utility operation that after expanding waits until the desired node exists, and replace all calls to expand() that do expect children by that. [1] Change-Id: I23ea6a7bc519692c0e9dbe480bb2eb8dfb96adc1 Signed-off-by: Thomas Wolf <>
2013-10-22Change test execution to find all tests instead of using suitesRobin Stocker1-27/+0
There are multiple problems with using suites: * They need to be kept up-to-date manually. There were some test classes which were not referenced by suites and therefore never executed in the Maven build. See parent changes for some examples. Before this change, the output said "Tests run: 266", after: "Tests run: 311". * When executing tests in Eclipse by selecting a project or package, tests in suites are executed twice. In case of hierarchical suites, it's even more than twice. Change-Id: Iaee4b36839e4ae2b3529e82e312d84ed30175b29 Signed-off-by: Robin Stocker <>
2013-04-24Remove unnecessary usage of the internal FileRepository classRobin Rosenberg3-6/+4
Change-Id: Iae7b4e550d75798dc66edf6c9e03ea826f072f33 Signed-off-by: Matthias Sohn <>
2013-03-22Eliminate file handle leaksLaurent Goubet2-2/+6
Running the SWTBot test suite on a Windows environment highlights insidious file handle leaks caused by JGit's WindowCache which keeps ".pack" files open for reading and thus locked for deletion until the repository is properly closed, but EGit might not keep a reference towards this repository in its cache, "forgetting" to close it when needed. This is mostly true for sub-modules. This patch also gets rid of other random errors, sometimes due to a .project not properly removed. Bug: 404121 Change-Id: I3a596fcabdb5225e9042e1ffae6b054c48d72d54 Signed-off-by: Matthias Sohn <>
2013-03-19Bump EGit version to 3.0.0 and require JGit 3.0.0Robin Rosenberg3-3/+3
JGit changed version, change EGit too since it's soo heavily dependet on JGit. Change-Id: I4927823ff3cd499246b5b85534116cb70015cb9d
2013-03-07Move UIText and UIIcons to the internal packageRobin Rosenberg3-3/+3
These are not part of the API and should therefore not be in a public package and also not checked for API compatibility. Change-Id: I8439adce61515177d36227c844d6284de700964f Signed-off-by: Matthias Sohn <>
2012-12-22Run "click context menu" synchronously where possible in testsRobin Stocker2-4/+4
This could further stabilize some tests, as running the context menu action synchronously makes sure that the action is complete before returning to the caller. The asynchronous variant is still necessary for when more UI interaction is required to complete the action. Change-Id: Id28b4cdc8b7e6ca6e993f736dcf70bb621cd8f0e
2012-07-16[findBugs] Make variables set in @Before non-staticRobin Stocker3-3/+3
Change-Id: I866eaa13b0d1a74be6ec8ef873ef864fcee0b032 Signed-off-by: Robin Stocker <> Signed-off-by: Matthias Sohn <>
2012-02-10[repoView] Add submodule add/sync/update supportKevin Sawicki4-0/+338
The Submodules node and all child repository nodes now have an Update and Sync action available from the context menu. Root repositories and 'Submodules' nodes now have an Add action that opens a wizard to configure a new submodule that will be configured in the parent repository and cloned on completion. Change-Id: I2afea7dca9e40a2748c10a7f835b2deae301ba73 Signed-off-by: Matthias Sohn <>

    Back to the top