
| Key: |
CIB-484
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Daniel Ostermeier
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 17/Jul/06 04:08 AM
Updated: 11/Dec/08 05:48 AM
|
|
| Component/s: |
Web UI,
Projects
|
| Affects Version/s: |
1.1.1
|
| Fix Version/s: |
x.x
|
|
|
During the add project setup wizard, we ask the user for the ant target they wish to use. At the moment, we do not provide any validation or feedback based on what the user enters. What we should do is parse the configured ant file, extracting all of the available targets and use these to
a) provide the user with a list of options based on the existing targets.
Something we should not do is prevent the user from entering an invalid value (ie: a target that does not exist). We should warn them of this problem, but not prevent them from continuing with there configuration. The user is in control after all.
|
|
Description
|
During the add project setup wizard, we ask the user for the ant target they wish to use. At the moment, we do not provide any validation or feedback based on what the user enters. What we should do is parse the configured ant file, extracting all of the available targets and use these to
a) provide the user with a list of options based on the existing targets.
Something we should not do is prevent the user from entering an invalid value (ie: a target that does not exist). We should warn them of this problem, but not prevent them from continuing with there configuration. The user is in control after all. |
Show » |
|