Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: Design, Patterns & Best Practices, Performance, Plugins and Lifecycle
-
Labels:None
-
Number of attachments :
Description
look into a way to avoid rerunning some heavy goals again unnecessarily.
For example, currently clover:check run after test will execute the tests again with clovered classes. It would be nice to fold that down onto the same lifecycle when it is known not to be harmful to the existing parts, but also keep it separate enough that packing won't include clovered classes, for example.
Activity
Vincent Massol
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Workflow | jira [ 35072 ] | Maven [ 37077 ] |
Jason van Zyl
made changes -
| Component/s | Plugins and Lifecycle [ 11340 ] | |
| Component/s | Performance [ 11981 ] |
Brett Porter
made changes -
| Component/s | Design & Best Practices [ 11341 ] | |
| Component/s | Plugins and Lifecycle [ 11340 ] |
Vincent Massol
made changes -
| Workflow | Maven [ 37077 ] | Maven New [ 46925 ] |
Jason van Zyl
made changes -
| Fix Version/s | 2.1 [ 11704 ] | |
| Fix Version/s | 2.1.x [ 13142 ] |
Brett Porter
made changes -
| Fix Version/s | 2.x [ 13145 ] | |
| Fix Version/s | 2.1 [ 13142 ] |