Community
Participate
Working Groups
It is unclear to the user what the connection is between using the "Run Ant" actions in the navigator, and running a script from the Ant view. In fact, there is no correlation. For example, if I have a config setup for a script that performs a refresh when run. However, when I add that script to the ant view and run it, the refresh does not happen. I beleive there would be a better user experience if we actually used the same launch config as the starting point (but allowed for dynamic target selection). Thus, when the user runs a script/target from the ant view, the starting point of the run is that of any existing launch config (i.e. create a working copy from the persisted config). Then, we set targets to be the selected targets, and run. As well, the user should be able to modify properties of the script from the ant view, via a "properties" pop-up on the script. This would open the launch config properties dialog on the associated config (creating one if none).
Assigning to Jared for comment.
I'd prefer to leave it as it is for now. If we can get a good Ant editor and an Outliner, we might not even want to keep the Ant View.
The Ant view will remain even with an Ant editor - it provides convenient access to more than on ant script. So we will need to address this issue either way. As implementers, we understand that the navigator actions run launch configs, and the ant view actions create/run temporary configs. However, users do not understand this concept. Running a script from the nvaigator, ant view, or eventually editor, needs to have some common base.
I've switched the Ant view's actions over to using the AntLaunchShortcut. Running from the Ant view now uses your configurations just like running from the Navigator or the Run menu. The only difference is that the targets specified in the config are overridden by the targets selected in the view. Please verify.
I verify that it works (actually quite nice). The only issue I see is that when there is more than one config for the script, the user has to choose which config to base the run on, which is a little disorienting. However, if a user works primarily in "Ant View" mode, then this will likely not happen (i.e. there will only be one config).
