Hi Tor

I noticed that the lint check works for app depending on aar file. However, 
if the app is depending on a library project, even if the lint.jar there 
and show up in  app/build/intermediates/exploded-aar , the custom rules are 
not picked up.

Is it expected?

Thanks

On Monday, November 18, 2013 9:50:48 AM UTC-8, Tor Norbye wrote:
>
> Lint now automatically looks for extra lint jar files supplied with 
> libraries. For example, the appcompat library (the AAR file that is) can 
> contain a lint.jar with custom rules that perform additional checks for 
> that library. (It doesn't yet, but I used that as a local test when adding 
> the support in lint for this). Then, any app that depends on this library 
> will automatically pull in these extra rules and apply those to the 
> project. This should work in Studio (with gradle projects) today. It should 
> also work with the gradle lint target, but the command line gradle 
> integration is still incomplete.
>
> Right now you have to manually assemble your AAR to contain the custom 
> lint rule jar, but the plan is for it to get automatically built if you 
> have a custom lint rule directory.
>
> -- Tor
>
>
> On Sun, Nov 17, 2013 at 9:26 AM, Patrick Hammond <[email protected] 
> <javascript:>> wrote:
>
>> If you have custom lint checks that don't make sense to provide in the 
>> core set of Android lint checks (they could be library specific, project 
>> specific, team coding conventions, etc), you need to manually copy those 
>> lint JARs to the current machine's lint tools settings directory (per 
>> http://tools.android.com/tips/lint-custom-rules, under 'Register Custom 
>> Jar File').  This doesn't feel very portable or flexible.  What I'd like to 
>> see is the ability to specify multiple custom lint checks in a project 
>> configuration to get this portability and flexibility.
>>
>> Thinking it through:
>>
>>    - This feature would probably start with being able to specify paths 
>>    to additional checks via the Lint CLI.
>>    - Support for declaring checks as dependencies via Gradle and/or 
>>    other build scripts. 
>>       - Ideally, you wouldn't need to also update another project 
>>       configuration to specify inclusion of the checks.
>>    - IDE support to manage declaring/managing the additional lint 
>>    checks (not sure what this looks like). 
>>
>> All that said, is there a design reason or constraint that would make 
>> this ill advised/impossible?  Is it something already on the roadmap, or 
>> now on the roadmap, and just needs some help?
>>
>> Thanks in advance!
>> Patrick
>>  
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "adt-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to