SweatSuite is an embodiment of the idea that convention
is better than configuration. It builds on the
conventions of Maven2 by adding common assumptions about
the development environment, reporting configuration,
and test suite.
Change the
parent
of your project to point to a preconfigured sweatSuite
POM and set a few properties that "fill in the
blanks" for the development environment of your
project.
Trying to improve quality by adding reports is like
trying to lose weight by weighing yourself more often.
SweatSuite will make it easier to see various aspects of
project quality, but it only helps if the project team
reads
and
acts
on the information.
Since SourceForge follows the same conventions for
it's projects, sweatSuite can work out much more of
the configuration automatically. Use the
POM designed for SourceForge projects
to take advantage of the additional information about
the development environment.
Use the generic
sweatsuite
artifact to engage the basic configuration. The basic
configuration includes numerous reports that are
activated by the
reporting
profile.
Because it doesn't have to be. Most archetypes are
designed to get the actual software started rather than
configure the project infrastructure. Having to make a
decision between sweatSuite and some archetype would be
an unnecessary pain. However, there is
an archetype to configure an existing project
.
