History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-484
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Daniel Ostermeier
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pulse

Parse Ant build file to support the ant project configuration process.

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


 Description  « Hide
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.

 All   Comments   Change History      Sort Order:
Daniel Ostermeier - 24/Jan/07 11:48 PM
1.2.x is now for bug fixes only as 2.0 development is making major incompatible code changes to the core, making support for development on two branches impractical.

Daniel Ostermeier - 11/Dec/08 05:48 AM
Trying to clean things up a little. We currently have a couple of very large buckets of tasks that are really not indications of our scheduling. What I am doing is for starters, moving all of the 2.x. items into x.x to indicate that they have not been scheduled. We can later go through these and pick up with ones that we intend to complete for an upcoming release.