-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle project view keeps project hierarchy #1612
Conversation
Implements microsoft#945 by parsing the project path which is found in the 'definition.script' property. The project path, which is unique for every subproject, is then used as key in the 'projectTreeItemMap'.
@microsoft-github-policy-service agree |
Thank you @jjohannes. I'm just back from vacation and will review this contribution ASAP. |
Thank you for the quick response and integrating this @jdneo. |
I found an issue about this change that some of the modules are in the wrong place: For example, here: the Clone and open the project https://github.com/microsoft/build-server-for-gradle can reproduce the error |
In microsoft#1612, the keys of this map were changed to the Gradle project path. This path is unique for each project within one Gradle build, but not if there are multiple Gradle builds loaded in one workspace by using: 'gradle.nestedProjects': true This change combined the old and new behavior by creating the Map key from two parts: (1) The root project folder which uniquely identifies the build (accessible via definition.projectFolder) (2) The Gradle project path that uniquely identifies a project inside the build
In microsoft#1612, the keys of this map were changed to the Gradle project path. This path is unique for each project within one Gradle build, but not if there are multiple Gradle builds loaded in one workspace by using: 'gradle.nestedProjects': true This change combined the old and new behavior by creating the Map key from two parts: (1) The root project folder which uniquely identifies the build (accessible via definition.projectFolder) (2) The Gradle project path that uniquely identifies a project inside the build Signed-off-by: Jendrik Johannes <jendrik.johannes@gmail.com>
In #1612, the keys of this map were changed to the Gradle project path. This path is unique for each project within one Gradle build, but not if there are multiple Gradle builds loaded in one workspace by using: 'gradle.nestedProjects': true This change combined the old and new behavior by creating the Map key from two parts: (1) The root project folder which uniquely identifies the build (accessible via definition.projectFolder) (2) The Gradle project path that uniquely identifies a project inside the build Signed-off-by: Jendrik Johannes <jendrik.johannes@gmail.com>
Implements #945 by parsing the project path which is found in the
definition.script
property. The project path, which is unique for every subproject, is then used as key in theprojectTreeItemMap
.