Skip to content
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

Merged
merged 2 commits into from
Jul 19, 2015
Merged

#159 Renamed resources leading with "__" #161

merged 2 commits into from
Jul 19, 2015

Conversation

ToxicBakery
Copy link
Contributor

Build tools "1.3.0 rc1" changed the rules for resources. This commit simply removes the lead "__" from the offending resources in the project.

@MGaetan89
Copy link

Maybe this PR could be the opportunity to use the Gradle resourcePrefix ?

@ToxicBakery
Copy link
Contributor Author

Sure but that seems like another issue to me. I just needed a quick fix to get a working build for my projects.

@ignaciogs
Copy link

+1

2 similar comments
@JohNan
Copy link

JohNan commented Jun 8, 2015

+1

@bagintz
Copy link

bagintz commented Jun 8, 2015

+1

@shekibobo
Copy link

@ToxicBakery Might also need to update the README.

@seviu
Copy link

seviu commented Jun 12, 2015

+1

10 similar comments
@gonzalocasas
Copy link

+1

@tianshan20081
Copy link

+1

@markiv
Copy link

markiv commented Jun 12, 2015

+1

@langerhans
Copy link

+1

@AndreasBackx
Copy link

+1

@leelei
Copy link

leelei commented Jun 15, 2015

+1

@drewhannay
Copy link

+1

@FrancisShi
Copy link

+1

@eccyan
Copy link

eccyan commented Jun 16, 2015

+1

@amusicegc
Copy link

+1

@artem-zinnatullin
Copy link

Please stop this "+1" hell.
16 июня 2015 г. 3:44 PM пользователь "Austin Musice" <
notifications@github.com> написал:

+1


Reply to this email directly or view it on GitHub
#161 (comment).

@bagintz
Copy link

bagintz commented Jun 16, 2015

+1 to artem's comment

@langerhans
Copy link

+1 @artem-zinnatullin's comment. Someone should merge this to stop this madness.

@TealOcean
Copy link

+1

4 similar comments
@dianvaltodorov
Copy link

+1

@marcoRS
Copy link

marcoRS commented Jun 22, 2015

+1

@linakis
Copy link

linakis commented Jun 22, 2015

+1

@pizza
Copy link

pizza commented Jun 22, 2015

+1

@ToxicBakery
Copy link
Contributor Author

Sigh...

@jacobtabak
Copy link

+1

@ToxicBakery
Copy link
Contributor Author

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.

@dangalg
Copy link

dangalg commented Jul 3, 2015

+18

@MGaetan89
Copy link

It seems to be working again with version beta4 of the Gradle plugin

@dangalg
Copy link

dangalg commented Jul 5, 2015

Where can I find beta 4?

@MGaetan89
Copy link

It's on jcenter.

You just need to change the version in your project build.gradle file.

@IgorGanapolsky
Copy link

But gradle beta4 doesn't work on Travis-ci. So this solution will
completely screw up automated builds for people!
On Jul 5, 2015 7:11 AM, "Gaëtan Muller" notifications@github.com wrote:

It's on jcenter
https://bintray.com/android/android-tools/com.android.tools.build.gradle/1.3.0-beta4/view
.

You just need to change the version in your project build.gradle file.


Reply to this email directly or view it on GitHub
#161 (comment).

@MGaetan89
Copy link

I have no issue with the Gradle plugin version 1.3.0-beta4 on Travis.
What error do you have?

@IgorGanapolsky
Copy link

@MGaetan89 You are right, it works with that version. I confused the issue with buildToolsVersion '23.0.0 rc2' - which does NOT work on Travis-ci.

Thanks for the advise, have some @changetip bitcoin $1 on me.

@MGaetan89
Copy link

No problem. Having a regular changelog for each Gradle plugin release would help more than guessing 😉

@pyricau
Copy link
Member

pyricau commented Jul 14, 2015

Sorry guys I've been really busy for a while. Looking.

@JakeWharton
Copy link
Collaborator

-1

@pyricau
Copy link
Member

pyricau commented Jul 14, 2015

:trollface: :trollface: :trollface: :trollface: :trollface: :trollface: :trollface:

Alright. Thank you for this PR, sorry for the wait. Seems like the full fix would be to remove the full manual prefix (__leak_canary_, not just __) for all resources, and then use Gradle resourcePrefix to set that to leak_canary.

@ToxicBakery
Copy link
Contributor Author

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.

@pyricau
Copy link
Member

pyricau commented Jul 14, 2015

Yes, if you do the change I'll merge, thanks.

@ToxicBakery
Copy link
Contributor Author

@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:
http://tools.android.com/tech-docs/new-build-system
0.10.0

  • Resource Prefix support.
    • Starting with Studio 0.5.8 Lint will warn you or resources not using the prefix.

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.
@pyricau
Copy link
Member

pyricau commented Jul 19, 2015

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">
Copy link
Member

Choose a reason for hiding this comment

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

Why did this change?

Copy link
Member

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.

@pyricau
Copy link
Member

pyricau commented Jul 19, 2015

Alright, LGTM. We also need to update the changelog.

pyricau added a commit that referenced this pull request Jul 19, 2015
#159 Renamed resources leading with "__"
@pyricau pyricau merged commit 5726f6a into square:master Jul 19, 2015
@pyricau
Copy link
Member

pyricau commented Jul 19, 2015

pyricau added a commit that referenced this pull request Jul 19, 2015
@ToxicBakery
Copy link
Contributor Author

Yeah np, signed.

@pyricau
Copy link
Member

pyricau commented Jul 20, 2015

Thanks!

@catupablo
Copy link

Hi, could you give me an estimated release date for the 1.4 version? Thanks :)

@pyricau
Copy link
Member

pyricau commented Aug 1, 2015

Sometimes in Q3, maybe.

Yky pushed a commit to Yky/leakcanary that referenced this pull request Feb 21, 2016
Yky pushed a commit to Yky/leakcanary that referenced this pull request Feb 21, 2016
Pengchengxiang pushed a commit to XLibrarys/leakcanary that referenced this pull request Jan 2, 2017
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.