Tasks Quick Launcher should remember last used project about eclipse-integration-gradle HOT 15 CLOSED

I would probably use the Quick Launcher with that improvement. Now the "Gradle Tasks" list is more fast to use.

from eclipse-integration-gradle.

possibly Tasks Quick Launcher just needs key binding to select project, e.g. F4

so that user wouldn't have to leave the keyboard

from eclipse-integration-gradle.

I'll try to implement something to address this request for 3.6.3 STS release.

from eclipse-integration-gradle.

Great, thanks Alex!

from eclipse-integration-gradle.

Quick Task Launcher dialog would set currently selected Gradle project
based on current selection in the workbench.
For example if you have a Gradle project selected in the Project Explorer
then if Quick Launcher is opened the selected project would be the Gradle
project selected in the Project Explorer. Furthermore, if a resource from
Gradle project is selected then the Quick Launcher would have the
resource's parent Gradle project set.
The problem is that if the selected project is not a Gradle project or
resource selected doesn't belong to a Gradle project. The project combo box
from the Quick Launcher doesn't have any project selected in that case. I
suspect that this is the use cases you're hitting.
I'm making the Quick Launcher to remember the last selected project such
that if selection in the workbench is not Gradle project then it would
become the project selected from the last time Quick Launcher was shown.
How does that sound? Or you are more in favour of remembering the project
for which task(s) were run in Quick Launcher?

On Thu, Nov 6, 2014 at 10:54 AM, Andre Azzolini [email protected]
wrote:

Great, thanks Alex!

—
Reply to this email directly or view it on GitHub
#53 (comment)
.

from eclipse-integration-gradle.

I think your suggestion is an improvement. It would also extend to selecting the correct project given the currently edited file if launched from a hotkey, which is awesome.

Today, if there is no context, it launches with the alphabetically first project selected. I think that behavior is ok, or launching with no selected project would be ok as well.

from eclipse-integration-gradle.

Alright. Thanks for the feedback. Changes are in.

from eclipse-integration-gradle.

👍

from eclipse-integration-gradle.

Thanks for adding this Alex! I'm looking forward to see this in the 3.6.3 STS which I read is scheduled to ship in December. Marc

from eclipse-integration-gradle.

I am using GGTS 3.6.3, and however its Gradle Quick task launcher was disabled suddenly, if I press (Ctrl+Shift+Alt+r) it won't work and doesn't open the dialog box.

Does anyone face before ?

from eclipse-integration-gradle.

Are there specific circumstances under which it became disabled? Does the project have Gradle nature? Is it a specific project? What’s in the error log at the time when action becomes disabled?

On Dec 23, 2014, at 01:11, chintanpanchal [email protected] wrote:

I am using GGTS 3.6.3, and however its Gradle Quick task launcher was disabled suddenly, if I press (Ctrl+Shift+Alt+r) it won't work and doesn't open the dialog box.

Does anyone face before ?

—
Reply to this email directly or view it on GitHub #53 (comment).

from eclipse-integration-gradle.

Which version of Gradle integration for eclipse or STS is it?

On Dec 23, 2014, at 01:11, chintanpanchal [email protected] wrote:

I am using GGTS 3.6.3, and however its Gradle Quick task launcher was disabled suddenly, if I press (Ctrl+Shift+Alt+r) it won't work and doesn't open the dialog box.

Does anyone face before ?

—
Reply to this email directly or view it on GitHub #53 (comment).

from eclipse-integration-gradle.

There is no error logs, and all the projects in my workspace are Gradle nature.
When I launch Quick Task of gradle it shows nothing not even a single error message.
Gradle version: 3.6.3

from eclipse-integration-gradle.

I can’t seem to be able to reproduce this issue with 3.6.3.
Would you be able to debug the problem?
If yes, then please clone the Gradle eclipse repository here: https://github.com/spring-projects/eclipse-integration-gradle https://github.com/spring-projects/eclipse-integration-gradle There is documentation available on the page. (The only difference from the doc is that toolingapi project became a Maven project and you’d have to run “mvn clean install” on it to download Gradle tooling api jars)
Once the code compiles run a runtime workbench, put breakpoints in ConsoleInplaceDialogActionDelegate and its super class, try to see why this action becomes disabled for you.

On Dec 23, 2014, at 06:15, chintanpanchal [email protected] wrote:

There is no error logs, and all the projects in my workspace are Gradle nature.
When I launch Quick Task of gradle it shows nothing not even a single error message.
Gradle version: 3.6.3

—
Reply to this email directly or view it on GitHub #53 (comment).

from eclipse-integration-gradle.

Thanks Alex,

I have found another solution, in that if we create another workspace than Quick Launch works as expected. So, It might be workspace specific issue

from eclipse-integration-gradle.