Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add notes relating to alternate lifecycles (eg for site) 

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163351 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Brett Leslie Porter 2005-02-13 03:54:12 +00:00
parent 734257981b
commit aa25e4562f
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
maven-core/src/site/apt/lifecycle/lifecycle-phases.apt
View File

@ -16,7 +16,7 @@ Maven Lifecycle Phases
* compile [plexus component or something else] * compile [plexus component or something else]
* process classes * process classes [eg JDO, coverage]
* generate test sources [generating junit tests] * generate test sources [generating junit tests]
@ -216,3 +216,24 @@ Notes for discussion:
direction, but when you factor inheritance into the mix, this could get direction, but when you factor inheritance into the mix, this could get
really sticky. really sticky.
[/Added, jdcasey/2005-01-23] [/Added, jdcasey/2005-01-23]
[Added, brett/2005-02-13: Inserting these as things left over from previous
mails to m2-dev that were pre-lifecycle]
Multiple lifecycles will be able to be used and defined - for example "site"
would have an additional lifecycle. This interface may even be available to
users, though strongly discouraged as the default lifecycles should accommodate
almost any use case.
As the site runs through, it will want to ensure that parts of the lifecycle
already complete are not run again unless the parameters change.
eg. For coverage - no need to compile again, but do add an additional
instrumentation step, then run the tests again on the new instrumented classes
(in a new directory, not over the top of the old ones).
To simplify this, we may actually allow some steps to re-run and rely on the
file timestamping to make it effecient.
[/Added, brett/2005-02-13]