Currently one is expected to define phases like +install.
This will be changed to install] to express "all phases in the lifecycle of <phase> before the <phase> in question".
Furthermore [install will be supported to express "all phases in the lifecycle of <phase> after the <phase> in question".
Another feature will be to define call on phases after a certain point.
For example:
The package] phase has been called previously and you want to finish the lifecycle but not deploy the artifact.
Now the phase-task package[,]deploy can be used.
Added Properties
r4m.lifecycle-task-request-calculator and r4m.lifecycle-task-request-calculator-on-fork
Rework Phase Tasks / Phase Ranges
Currently one is expected to define phases like
+install. This will be changed toinstall]to express "all phases in the lifecycle of<phase>before the<phase>in question".Furthermore
[installwill be supported to express "all phases in the lifecycle of<phase>after the<phase>in question".Another feature will be to define call on phases after a certain point.
For example:
The
package]phase has been called previously and you want to finish the lifecycle but not deploy the artifact. Now the phase-taskpackage[,]deploycan be used.Added Properties
r4m.lifecycle-task-request-calculatorandr4m.lifecycle-task-request-calculator-on-forkthe two properties following values & effects:
declared: treats<phase>like[<phase>]sequential: treats<phase>like<phase>]