Community
Participate
Working Groups
I created a new Gradle launch configuration, but I can't run it unless I choose a working directory. I think it should be extremely reasonable to automatically fill it with a value of ${project_loc} when the configuration is created, so that the user does not have to do that explicitly. One obstacle to this is that I just saw there's no reference to any project in the Gradle launch configuration, contrary to what happens with many other launch configurations. This makes me wonder which build.gradle file will be used by the launch configuration. (please note I've just one project in the workspace now, is Buildship smart enough to hide the project selection UI component because of this reason?).
The working directory is the place where you should specify the workspace project. It is a bit more abstract since one can select not only a workspace project but also an external location to execute a Gradle build. Consequently, there is no way to automatically fill the working directory.
I don't understand the "consequently" part. The fact that you *may* specify an external location does not mean you can't default it to ${project_loc} if that's the reasonable choice in 90% or more of cases. The problem of the absence of the project reference in the launch configuration remains though.
We are in the process of migrating our issues to GitHub. We've created an issue for this report: https://github.com/eclipse/buildship/issues/337 Let's continue the conversation there.
