Community
Participate
Working Groups
A thing missing to make Ant integration as smooth as possible... An action simulating or working like ant -find build.xml It is what e.g. Emacs JDEE ant support does when it starts an ant build. It uses the current selected resource (buffer in emacs) and search for a build.xml file from here and up to the root of the filesystem - or until it finds a build.xml and then ant starts chewing on this build.xml.... And if the entering of which target one should use could be done with keyboard and a little help of completion instead of using the mouse to select a checkbox from a list of maybe 30 targets then it would be heaven :) What it is so great about this ? It is great because then you are not forced to go look for the correct build.xml manually - neither in the package/resource view or in the predefined ant targets in the external tools menu - eclipse just takes the best guess and in this situation it will often be the correct one as the build.xml related to a resource is normally stored in one of its parent directories - and their can only be one build.xml when searching like that :) so - please add that to your goals for ant support, it should be breeze to implement :)
-find is not new to 1.5.1 (it is available in 1.4.1) we just have not exposed the functionality. Changed summary accordingly.
The Ant view supports a "find" operation. It finds all files in the workspace with a specific name (which is settable in the Ant View perferences). Is this sufficient?
Another request for -find.... *** This bug has been marked as a duplicate of 26455 ***
That is not sufficent. It does not solve the problem of still having to manually choose EXACTLY which build file to use (I got 25 in my antview right now) and THEN have to choose which target to run. The -find option should make it possible not to have to choose which build file to run as Ant can figure that out it self by just having it run in the directory of the current open resource/file. Secondly selection of the target should be optional! If none is selected then just run the default target - and I should not need to "deselect" the default target to change my wanted target. And I have reopened the bug as #26455 is an related but different story.
I believe the "find" feature is described by bug 26455 - i.e. locate the ant script to run in the current or parent directory. The "find" feature could be implemented to prompt for a target, or run the default target (based on a preference setting). Is there anything missing from 26455 now? Can we mark this as a duplicate?
It can be marked an duplicate if you just remember the thing about searching for the "neareste" build.xml (where nearest is from current directory upto the root of the filesystem) Secondly it should be possible as you describe just to run the default target or optionally enter another target. looking forward to it :) *** This bug has been marked as a duplicate of 26455 ***
