2008/4/18, Giovanni Azua <[EMAIL PROTECTED]>: > > Ciao Antonio, > > Antonio Petrelli wrote: > > > In fact the problem is with *old* files :-( > > > > > Then an alternative way would be using find/sed once and having the coding > style xml config for new files.
It's really hard to fix 600+ files :-( I personally find that the perfect combination is coding std xml config + > jalopy + checkstyle because checkstyle only signals mistakes and coding > style config generates new files code respecting the defined conding std in > the first place. +1 But the problem here is the lack of license file. I don't think that Jalopy can help here, at least not for JSP, FTL etc, files. Using a maven plugin for this would be nice but maybe better if activated on > demand only as part of a profile and not running for every build. Well, in fact the "license:format" goal will be run on-demand, only when needed, the license:check (similar to RAT maven plugin, I don't know even if it is necessary) will be activated in the "release" profile. As I understood for your comments it is not possible because you have > placeholders replaced in every build ... Maybe I have not been clear: there are files completely without license headers, without placeholders. The license plugin helps putting it in the right places. The placeholders (variables) I was referring to are in the "txt" file containing the header to add to files. See: http://code.google.com/p/maven-license-plugin/wiki/Configuration (search for "variable replacement"). Thanks Antonio
