How to limit the built-in functionality of BuildShip (gradle eclipse)?

Now that I am using gradle for all my new developments, I am having problems with BuildShip functions that I really don't need.

For example, when I click the Run button, when I have a unit test open in Eclipse, I want it to run only as a JUnit test, . But gradle inserted its own hooks and parameter, which means an extra click or keystroke behind the single-line hotkey that I assigned to run, that I can say that I want JUnit. (The gradle test actually runs all the tests, which takes several minutes.).

Question : Is there a way to remove this hook in gradle without diving into the source code and spontaneous work?

This is not the only intervention (intervention in launching the latter is another), but it is my # 1 annoyance about BuildShip.

Essentially, I want this popup to not stop.

+7
java eclipse junit gradle buildship
source share
1 answer

Indeed, you cannot change the prompt for available launchers, but you can change the default hotkeys associated with each launcher and directly use the one you prefer.

In Windows> Preferences> General> Editor> Keys, you can get a list of available hotkeys. Filter the (long) list by typing the test as shown below:

enter image description here

As you can see, you have several mappings for running JUnit tests: Gradle, JUnit runner, Maven.

The default configuration for the JUnit runner is Alt+Shift+X,T , which is not very user friendly.

I changed it to a more compressed Alt+U down in the Binding option and applied the changes. Now you can run any JUnit test in your open editors without any prompts, just type Alt+U , and the JUnit runner will run automatically for this single unit test.

+2
source share

All Articles