[news.eclipse.tools.jdt] Re: Auto clean up

[Hasan Ceylan <hceylan@xxxxxxxxxx>]

Benno Baumgartner wrote:
> Hasan Ceylan wrote:
> > Please ignore this post. JDT team seems to be one step ahead.
>
> :-) we do our best. There is no sort members (yet) see 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=37496
>
> Just out of interest: What other clean ups would you enable on save?

Hello Benno,
you certainly do it very well. ;)

I later noticed that but hadn't posted back again yet.
As I am a human-robot build to obey clean coding rules, I enable 'em 
all. But the most valuable ones would be sort members (due to cvs diff 
prob), format source, "use this for qualifier for field access", unused 
imports, @override annotation, generated serial version UID...

By the way, if these are set in the preferences, do they get honored 
during the preferences export/import functionality.

Because, I also force the coding styles and (now cleanup) to my team.

I would like the idea of dumping the preference in the cvs together with 
these settings.

Regards,
Hasan Ceylan

> Benno
>
> > Hasan Ceylan wrote:
> > > Hello,
> > >
> > > I always resort the members, format the sources before I save them. I 
> > > would also cleanup stuff like the ones in the cleanup dialog. Since I 
> > > am obsessed with the coding cleanly, sometimes sorting members give 
> > > me headaches. This is as follows,
> > > - I start to edit a source file.
> > > - Introduce new methods and / or fields.
> > > - commit to cvs before sorting the members.
> > > - later, edit the source again. This time sort the members.
> > > - Others edit the same source. They end up with a long list of 
> > > scrambled compare editor to resolve conflict.
> > >
> > > I think for those like me, a switch somewhere to set auto-clean up 
> > > before save would be much appreciated.
> > >
> > > If other users/JDT committers find this idea worthwhile, I will open 
> > > up a request for enhancement in the JDT bugzilla.
> > >
> > > Hasan Ceylan