streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sblackmon <>
Subject Re: [DISCUSS] Coding style conventions + auto-formatting
Date Tue, 08 Nov 2016 16:39:05 GMT
I’ve set up checkstyle and scalastyle (bound to validate phase, no fail on error) over in

and started refactoring code to match the google style in

The google_style.xml that ships with the plugin needs a few tweaks:

- we need org.apache.streams.* to be at the top of the import list, not*
- 100 characters per line isn’t enough.  I think we can make 140 work. 

So I still need to figure out where / how to publish a modified check style file so that works
transparently across all three repos.

If anyone has specific ideas about how to systematically modify existing code to match the
style guide, please let me know over in

On November 2, 2016 at 6:11:51 AM, Praveen Adlakha ( wrote:

Hi All,  

+1 for maven checkstyle plugin it's a widely accepted solution to the  
problem at hand.  

Minor nit: We can think in terms of creating a different profile to run  
checkstyle plugin it kind of ease the development when a developer is  
working on enhancements which require a lot of code.  


On Sat, Oct 29, 2016 at 12:28 AM, Timothy Spann <>  

> >  
> +1 for Google. Easy to import into any IDE and enforced with  
> checkstyle.  
> >  
> > -  
> >  
> com/twitter/common/  
> >  
> > -  
> >  
> > I'm sure there are more. Thoughts?  
> >  
> > Whatever happens, I'd suggest it just get enforced via Maven so we  
> don't  
> > have to kick PRs back and forth or keep discussing it. To that  
> effect I  
> > opened  
> And can check that from IDEs as well.  
> Tim Spann  

The information contained in this communication is intended solely for the  
use of the individual or entity to whom it is addressed and others  
authorized to receive it. It may contain confidential or legally privileged  
information. If you are not the intended recipient you are hereby notified  
that any disclosure, copying, distribution or taking any action in reliance  
on the contents of this information is strictly prohibited and may be  
unlawful. If you have received this communication in error, please notify  
us immediately by responding to this email and then delete it from your  
system. The firm is neither liable for the proper and complete transmission  
of the information contained in this communication nor for any delay in its  

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message