Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0-alpha-3
-
Fix Version/s: 3.x / Backlog
-
Component/s: Plugins and Lifecycle
-
Labels:None
-
Complexity:Expert
-
Number of attachments :
Description
For example pom.build.outputDirectory (classes directory) should inherit from pom.build.directory. Same for all properties that are used to generate build data.
Why? Becasue otherwise it's downright impossible to change the location of the target directory (pom.build.directory) as you don't know beforehand all the plugins that are part of the lifecycle and how many properties they each have and their name.
For example in the clover plugin I need to set the target dir to another location so that main build data is not compromised. I can't do it as I can't controll all the properties that could possibly exist. I'd just like to set the pom.build.directory to a new value and be done with it.
Issue Links
Activity
Vincent Massol
made changes -
Brett Porter
made changes -
| Fix Version/s | 2.0-beta-1 [ 11040 ] | |
| Environment | ||
| Description |
For example pom.build.outputDirectory (classes directory) should inherit from pom.build.directory. Same for all properties that are used to generate build data. Why? Becasue otherwise it's downright impossible to change the location of the target directory (pom.build.directory) as you don't know beforehand all the plugins that are part of the lifecycle and how many properties they each have and their name. For example in the clover plugin I need to set the target dir to another location so that main build data is not compromised. I can't do it as I can't controll all the properties that could possibly exist. I'd just like to set the pom.build.directory to a new value and be done with it. |
For example pom.build.outputDirectory (classes directory) should inherit from pom.build.directory. Same for all properties that are used to generate build data. Why? Becasue otherwise it's downright impossible to change the location of the target directory (pom.build.directory) as you don't know beforehand all the plugins that are part of the lifecycle and how many properties they each have and their name. For example in the clover plugin I need to set the target dir to another location so that main build data is not compromised. I can't do it as I can't controll all the properties that could possibly exist. I'd just like to set the pom.build.directory to a new value and be done with it. |
Brett Porter
made changes -
| Priority | Major [ 3 ] | Blocker [ 1 ] |
Brett Porter
made changes -
| Assignee | Brett Porter [ brettporter ] |
Brett Porter
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Brett Porter
made changes -
| Status | In Progress [ 3 ] | Open [ 1 ] |
Brett Porter
made changes -
| Priority | Blocker [ 1 ] | Major [ 3 ] |
Vincent Massol
made changes -
| Workflow | jira [ 35502 ] | Maven [ 37155 ] |
John Casey
made changes -
| Assignee | Brett Porter [ brettporter ] | John Casey [ jdcasey ] |
John Casey
made changes -
| Remaining Estimate | 6 hours [ 21600 ] | |
| Original Estimate | 6 hours [ 21600 ] |
Brett Porter
made changes -
| Fix Version/s | 2.0-beta-1 [ 11040 ] | |
| Fix Version/s | 2.0-beta-2 [ 11861 ] |
Brett Porter
made changes -
| Fix Version/s | 2.0-beta-2 [ 11861 ] | |
| Fix Version/s | 2.1-beta-1 [ 11704 ] | |
| Assignee | John Casey [ jdcasey ] | |
| Original Estimate | 6 hours [ 21600 ] | |
| Complexity | Expert | |
| Remaining Estimate | 6 hours [ 21600 ] |
Vincent Massol
made changes -
Vincent Massol
made changes -
| Workflow | Maven [ 37155 ] | Maven New [ 48090 ] |
Jason van Zyl
made changes -
| Fix Version/s | 2.1.x [ 13142 ] | |
| Fix Version/s | 2.1 [ 11704 ] |
Brett Porter
made changes -
| Fix Version/s | 2.1 [ 13142 ] | |
| Fix Version/s | 2.x [ 13145 ] |
Jason van Zyl
made changes -
| Issue Type | Wish [ 5 ] | New Feature [ 2 ] |
Brett Porter
made changes -
| Fix Version/s | 3.x [ 13145 ] | |
| Fix Version/s | Backlog [ 16138 ] |