-
Notifications
You must be signed in to change notification settings - Fork 4k
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
#159 Renamed resources leading with "__" #161
Conversation
…review build tools "1.3.0 rc1"
Maybe this PR could be the opportunity to use the Gradle |
Sure but that seems like another issue to me. I just needed a quick fix to get a working build for my projects. |
+1 |
2 similar comments
+1 |
+1 |
@ToxicBakery Might also need to update the README. |
+1 |
10 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
Please stop this "+1" hell.
|
+1 to artem's comment |
+1 @artem-zinnatullin's comment. Someone should merge this to stop this madness. |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
Sigh... |
+1 |
That is a good question, I suggest doing what I did internally. Fork it and repackage it for now in your local repos with this patch applied. |
+18 |
It seems to be working again with version beta4 of the Gradle plugin |
Where can I find beta 4? |
It's on jcenter. You just need to change the version in your project |
But gradle beta4 doesn't work on Travis-ci. So this solution will
|
I have no issue with the Gradle plugin version 1.3.0-beta4 on Travis. |
@MGaetan89 You are right, it works with that version. I confused the issue with Thanks for the advise, have some @changetip bitcoin $1 on me. |
No problem. Having a regular changelog for each Gradle plugin release would help more than guessing 😉 |
Sorry guys I've been really busy for a while. Looking. |
-1 |
Alright. Thank you for this PR, sorry for the wait. Seems like the full fix would be to remove the full manual prefix ( |
Do you want me to update this PR or close it then? I can make that change if that is what you want from this. |
Yes, if you do the change I'll merge, thanks. |
@pyricau actually have the time to look at this today and reading up I just want to make it clear that resourcePrefix is a lint utility and not a rename utility. Using a prefix of 'leak_canary_' lint will fail the build for resources that do not use that prefix inside the library. This seems like the correct and desired effect but it does mean the my original change will remain and more resources will now need to be renamed. For reference:
Pretty sure they meant 'warn you of resources' not 'or' |
…review build tools "1.3.0 rc1" - Added resourcePrefix lint check to validate all resource names are correct.
Yep, I talked to Tor and he mentioned that. |
@@ -15,6 +15,6 @@ | |||
~ limitations under the License. | |||
--> | |||
<resources> | |||
<style name="__LeakCanary.Base" parent="android:Theme"> | |||
<style name="leak_canary_LeakCanary.Base" parent="android:Theme.Holo"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, git is being bad at diffing.
Alright, LGTM. We also need to update the changelog. |
#159 Renamed resources leading with "__"
Actually, @ToxicBakery, can you sign the CLA here: https://docs.google.com/a/squareup.com/forms/d/13WR8m5uZ2nAkJH41k7GdVBXAAbzDk00vxtEYjd6Imzg/viewform?ndplr=1&formkey=dDViT2xzUHAwRkI3X3k5Z0lQM091OGc6MQ Otherwise I'll have to revert that PR. |
Yeah np, signed. |
Thanks! |
Hi, could you give me an estimated release date for the 1.4 version? Thanks :) |
Sometimes in Q3, maybe. |
square#159 Renamed resources leading with "__"
square#159 Renamed resources leading with "__"
Build tools "1.3.0 rc1" changed the rules for resources. This commit simply removes the lead "__" from the offending resources in the project.