buildship
buildship copied to clipboard
Allow Buildship through a View show the Gradle's Daemons created by the IDE itself
Expected Behavior
With Buildship installed either STS or Eclipse. Through the IDE itself, for example with a new View available or other approach, show the Gradle's Daemons but only created by the STS/Eclipse itself
- Observation by Gradle's Daemon I mean: GradleDaemon/GradleMainWrapper/Kotlin[Daemon/Thread]/Runner, it can be any of them or even many of them, by experience, the latter. It happens when a Gradle task is executed and it generates the execution/creation of other threads.
Current Behavior
Does not exist a way through the IDE itself to see what Gradle's Daemon was o were created by the IDE itself - it through Buildship where it executes any Gradle's Task. An approach to work around this is use the terminal and use the jps
and try to guess what thread was created by the IDE ("guess" - because could exists other threads created by other app based on Java - based on Gradle or not). Consider the scenario where the developer has no idea about the jps
command and the developer only works through gradlew --status
and gradlew --stop
.
The situation to resolve is about when some tasks would be executed by command and other through the IDE, why take this approach? - I found and reported the following experience and issue for example:
Where the solution is work through either terminal or add an extra parameter. So, now you can see why would be mandatory use both or any of them.
Context
Is not critical, but exists Gradle Daemon Threads accessing at the same to the same resources, so locks events happens and some Threads must be stopped, it through gradlew --stop
and by jps
(using kill -9 ID
)
Other situation is about the following experience that I had:
Here is tricky to do realise how fix the situation, so here is very important know what are the Gradle's Daemons created by the STS itself through Buildship