just a suggestion ;) it is possible to export/import a distinct set of preferences as well... In that case everything would be self-contained.
On Thu, Oct 30, 2008 at 1:23 PM, Alex Grönholm <[EMAIL PROTECTED]> wrote: > Daniel S. Haischt kirjoitti: >> >> it's as well possible to export your complete Eclipse preferences >> AFAIK which should then >> include the source code style settings. >> >> > > I don't think anyone wants to import ALL of my Eclipse preferences. >> >> The preferences then can be imported per workspace... >> >> >> On Thu, Oct 30, 2008 at 11:33 AM, Alex Grönholm >> <[EMAIL PROTECTED]> wrote: >> >>> >>> Jacek Laskowski kirjoitti: >>> >>>> >>>> On Thu, Oct 30, 2008 at 9:24 AM, Alex Grönholm >>>> <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>> >>>>> >>>>> AFAIK you have to import them manually through project settings -> Java >>>>> Code >>>>> Style. >>>>> >>>>> >>>> >>>> I wonder how we could enforce them before commit? There's a maven >>>> plugin for checkstyle, but I wouldn't like having code styles in more >>>> than one place. Is there a way to use the eclipse code style in a >>>> checkstyle-based plugin? Could it be converted to support IDEA, >>>> Netbeans? >>>> >>>> Jacek >>>> >>>> >>> >>> I meant these to be recommendations rather than something to be strictly >>> enforced. Those definition files are more like a convenience that makes >>> it >>> easier for Eclipse users to follow the code conventions for this project. >>> If >>> anyone manages to produce similar files for NetBeans or IDEA, so much the >>> better. >>> >>> > >
