build module POM.
2) It is a *major* pain to have a build fail simply because the code
is not formatted according to the Checkstyle and PMD conventions being
used in ServiceMix. So I've taken a stab at creating a code formatter
profile for Eclipse and some quick docs located here:
is a *major* pain to have a build fail simply because the code
> is not formatted according to the Checkstyle and PMD conventions being
> used in ServiceMix. So I've taken a stab at creating a code formatter
> profile for Eclipse and some quick docs located here:
This prevents a user
me day there should be all components refactored and the checkstyle
will be enabled in only one POM.
> 2) It is a *major* pain to have a build fail simply because the code
> is not formatted according to the Checkstyle and PMD conventions being
> used in ServiceMix. So I've taken a sta
it simply means that the checks wont be
> configured and activated :-)
How does an empty profile prevent the invocation of Checkstyle and
PMD? Sounds like Maven voodoo.
Bruce
--
perl -e 'print
unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://geronimo.ap
Note that you can disable the checks by adding -Pnochecks on the
command line iirc.
On 7/26/07, Kit Plummer <[EMAIL PROTECTED]> wrote:
On 7/25/07, Bruce Snyder <[EMAIL PROTECTED]> wrote:
>
> On 7/25/07, Kit Plummer <[EMAIL PROTECTED]> wrote:
>
> > As long as I can "comment out" the feature at on
setup.eclipse profile that REALLY gets things
setup in eclipse. (goes way beyond eclipse:eclipse) It injects the CXF
checkstyle rules into the workspace, sets the workspace warning levels
appropriately, injects the code format template, import order, etc
For each project, it also sets u
On 7/25/07, Bruce Snyder <[EMAIL PROTECTED]> wrote:
On 7/25/07, Kit Plummer <[EMAIL PROTECTED]> wrote:
> As long as I can "comment out" the feature at one place I don't mind the
> styleguide stuff. But, you are right...seems like it would be more of a
> pre-commit hook thing.
Well the problem
