| Key: |
CIB-1576
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Stephen Nesbitt
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 29/Jul/08 04:33 PM
Updated: 12/Dec/08 04:38 AM
|
|
| Component/s: |
Build core
|
| Affects Version/s: |
2.0.9
|
| Fix Version/s: |
2.x
|
|
|
Here's the scenario. My projects hierarchy looks like this: global project template -> ant build template - IRModeler CI Template -> IRModeler Dev
On the IRModeler CI Template I defined a property ir.build.targets.
This morning I realized that I had defined the property at the wrong level and that it shouls be defined as part of the ant build template. Currently pulse refuses to let me create that ir.build.targets property on the ant.template because it is defined in a child project. To fix this I have to: 1) find the child templates where it is defined, 2) delete the property for every child instance, 3) add it to the ant-template and 4) reset it on all the child templates.
It would be more elegant if Pulse would offer me the opportunity to do this work for me. That is something to the effect - "Do you want to abstract this property"
|
|
Description
|
Here's the scenario. My projects hierarchy looks like this: global project template -> ant build template - IRModeler CI Template -> IRModeler Dev
On the IRModeler CI Template I defined a property ir.build.targets.
This morning I realized that I had defined the property at the wrong level and that it shouls be defined as part of the ant build template. Currently pulse refuses to let me create that ir.build.targets property on the ant.template because it is defined in a child project. To fix this I have to: 1) find the child templates where it is defined, 2) delete the property for every child instance, 3) add it to the ant-template and 4) reset it on all the child templates.
It would be more elegant if Pulse would offer me the opportunity to do this work for me. That is something to the effect - "Do you want to abstract this property"
|
Show » |
|
Make moving property from child to parent project easier 
These sorts of configuration "refactorings" are something we are keen to add support for. They can be surprisingly difficult to do in general, both the back and front ends, but not always. If this one turns out simple it may make 2.0, but some others will be held back for future releases.
To alleviate some of the problems we do aim to add better navigation between parents and children in the UI - for example if you are in the properties for "ant build template" you should be able to get to the properties in its parent and children with one click, rather than having to switch to the hierarchy, choose the new project, then navigate to the properties.