It appears that I *do* have the settings in my workspace in the checkout, but that somehow not everybody has them (completely) applied.
For example a file that I saved was wrapped because it extended the 100 character limit that is in eclipse settings, but the original line was just one. Martijn On Tue, Sep 25, 2012 at 3:37 PM, Martijn Dashorst <[email protected]> wrote: > I'm not sure who is using eclipse or some other IDE, but currently I > don't have the proper formatting settings in my local checkout of > Wicket. AFAIR we used to have the formatting rules specified. > > I don't know whether m2eclipse supports updating the eclipse > formatting settings from a jar file, but fortunately the > maven-eclipse-plugin does (and isn't a resource hog for your average > day Java coding). > > At topicus we have a jar file (topicus-eclipse-settings-0.1.jar) that > contains all settings for eclipse that are relevant for working in a > team: centralized formatting rules, etc. We deploy this through our > maven repository and let the maven-eclipse-plugin update these > workspace settings whenever you run mvn eclipse:eclipse > > I consider this a really good way of using and sharing settings, and > I'd like to propose to do the same for Wicket. > > For this to happen, I would like to create a project in our subversion > repository (wicket-common/wicket-eclipse-settings/) that contains our > formatting settings, get the settings from one of you guys, release it > to maven central, and let the maven-eclipse-plugin depend on it such > that with a new mvn eclipse:eclipse the project will have the correct > settings. > > The benefit is that the eclipse settings are no longer part of the > "official" wicket checkout, and are only applied when someone is using > Eclipse—hence no longer 'polluting' the tree. > > Who is with me? > > Martijn > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com
