Skip to content

Use project.name instead of hardcoding 'app' in Android Gradle Plugin.#555

Merged
bretthoerner merged 1 commit intomasterfrom
android-plugin-project-name
Feb 9, 2018
Merged

Use project.name instead of hardcoding 'app' in Android Gradle Plugin.#555
bretthoerner merged 1 commit intomasterfrom
android-plugin-project-name

Conversation

@bretthoerner
Copy link
Copy Markdown

Fixes #554

@bretthoerner bretthoerner merged commit d5569c7 into master Feb 9, 2018
@bretthoerner bretthoerner deleted the android-plugin-project-name branch February 9, 2018 14:44
Copy link
Copy Markdown

@ruZZil ruZZil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

${project.projectDir} instead of the whole ${project.rootDir.toPath()}/${project.name} would be a broader solution. We have our project in a subfolder, ie, apps/. Using just ${project.projectDir} in here skipps the apps/ folder in our structure..

@bretthoerner
Copy link
Copy Markdown
Author

@ruZZil do you know if "${project.rootDir.toPath()}/${project.name} can always safely be replaced with ${project.projectDir.toPath()} then?

@ruZZil
Copy link
Copy Markdown

ruZZil commented Mar 8, 2018

I believe so. Please view #563. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants