- This topic has 7 replies, 5 voices, and was last updated 15 years, 7 months ago by
.
-
Posts
-
The run ant build in milestone 2 has what I consider to be a serious flaw. In the 6.5 versions and below, I could choose to “Run Ant Build…” one time and set the target. Then every consecutive run of ant build (with keystrokes Alt-Shift-Q-X) would continue to use that target. Now if I do thing same thing. Every consecutive run with the keystrokes tries to run the “all” target and not the last configuration.
On top of that, on at least OS X and Debian Linux, this entire “Run as Ant Build” doesn’t seem to show up anymore. I tried multiple machines (no Windows machine though) and in all 7.0M2 installations it was missing.
dthompson,
The last-run default behavior changed between Eclipse 3.3 (MyEclipse 6.5) and Eclipse 3.4 (MyEclipse 7.0), that might be why you are seeing this change? You can try adjusting it back to the default of “last run” and see if it behaves a bit better?
It’s a platform default change unfortunately. I prefer the old behavior as well, not really sure why they changed it.
So, evantually the only reliable way to set a (temporary) different target is to change the default=”” setting in the build file?
Maybe someone has a better solution, fix or workaround? (besides from switching to Maven 😉 )
TIA
TonWell, I’ll have to answer my own question this time 😉
Some observations:
1) Setting the default target of the build.xml to empty doesn’t work. Pressing Alt-Shift-X,Q simply runs no target, even though Ant is started and the build file is ‘executed’.
2) Selecting the build.xml, context-menu (Shift-F10), Run As, Ant Build… shows the selection, but choosing a different target all by playing the keyboard is quite cumbersome, or at least challengingInvestigation on the Eclipse.org site has leaned me that this ‘feature’ is, as said before, a technologically driven platform change, and it is most likely not going to be ‘reverted’. There does not seam to be anybody urged to treat this as a bug, aka omission.
There is however some light at the end of the tunnel.
At least 9 last run sessions are added to the list of ‘External Tools’ available from the Run menu. During selection of a target, the name for the ‘configuration’ can be set, default being “<ProjectName> build.xml”. Changing that to “<ProjectName> build.xml build” or “<ProjectName> build.xml package”, reflecting the target selected, makes these different configurations easily recognizable from the External Tools menu. By default, the next configuration saved (with the same name), gets (1) and (2) up to (8) appended, which isn’t much comprehensible.
These names can (optionally) be changed afterward from the Run/ External Tools/ External Tools Configurations menuitem.
Using this technique gives (me) the alternate key-sequence Alt-R,E,1 for the last run ‘External Tool’, and it also opens the menu, so I can decide whether to press 1, 2, 3 or 4 for my required (preset) build-target. The last one selected gets on top of the list, so don’t bother to remember the numbers assigned.Now if only we could assign a user defined key mapping to this dynamic menuitem, then all would be perfect again…
HTH
Ton
