Details
-
Type:
Task
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Documentation Deficit
-
Component/s: Documentation: General
-
Labels:None
-
Complexity:Novice
-
Number of attachments :
Description
Sample topics/themes (based on mailing lists):
1) Why Choose/Use Maven:
- How does using Maven change my every day job?
- How does using Maven make my code better?
- I'm a developer that uses Maven, how do I get other developers to adopt Maven when they say "I've got an IDE
that compile's my java code and don't need anything else." - I'm a developer that uses Maven, how do I get my manager(s) to adopt Maven?
2) Build Basics:
Why use a CI server?
How do I use CI with Maven:
--With Continuum
--with CruiseControl
--with Anthill
Why use a SCM?
How do I use my SCM and Maven:
--with CVS
--with subversion
--with (tbd)
Why Perform Unit Testing?
How do I perform unit testing in Maven:
--with Junit
--with Cactus
Why Apply Code Coverage?
*How to apply code coverage to Maven:
--with Clover
--with Jcoverage
--with Corbetura
3) Maven-specifics:
When/Why should I use M1
When/Why should I use M2
When, Why should I set up a multi-project?
Issue Links
| This issue relates to: | ||||
| MNG-1494 | Create comprehensive m2 feature list |
|
|
|
Aside from the "Why Choose/Use Maven", is there really a need for the "Why XXX" sections? I view "Why perform Unit Testing" or "Why use CI" as issues to be dealt with in a "Unit Testing" or "CI" document. HOW to use those with Maven, definitely - but why?