Maybe we could store the configuration files in the repo. E.g. Apache Camel does that in a way for multiple IDEs: https://github.com/apache/camel/tree/master/buildingtools https://github.com/apache/camel/tree/master/etc
Jan > -----Ursprüngliche Nachricht----- > Von: Charles Duffy [mailto:char...@dyfis.net] > Gesendet: Sonntag, 12. Januar 2014 19:11 > An: Ant Developers List > Betreff: Re: Ivy Code formatting > > +1 > > > On Sun, Jan 12, 2014 at 11:14 AM, Jean-Louis Boudart < > jeanlouis.boud...@gmail.com> wrote: > > > Hi there, > > > > While fixing a bug i noticed that ivy source code was not fully > formatted. > > Eclipse formatter is not exported as a plain file but present through > > eclipse project preferences in .settings folder [1]. > > > > Considering .settings folder is already commited i suggest to > activate > > "Saved actions" to apply on each save : > > > > - code formatting > > - organize import > > > > > > I also suggest to apply formatting on whole project (could be done in > > a few clicks with cleanup feature in eclipse). > > > > Are you in favor of those code modifications ? > > > > We could take the opportunity to cut this before 2.4.0 release. > > > > PS: This could aslo applied on others subprojects (ant for example) > > > > [1] > > > > > https://svn.apache.org/repos/asf/ant/ivy/core/trunk/.settings/org.ecli > > pse.jdt.core.prefs > > > > -- > > Jean Louis Boudart > > Independent consultant > > Apache EasyAnt commiter http://ant.apache.org/easyant/ > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
