----- Original Message ----- 
  
  
  Sent: Tuesday, October 22, 2002 8:49 
  AM
  Subject: Re: [platform-ant-dev] Ant 
  integration in Eclipse
  
  Great ideas - but one thing is still 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 :)
   
  /max
  
    ----- Original Message ----- 
    
    
    Sent: Monday, October 21, 2002 6:54 
    PM
    Subject: [platform-ant-dev] Ant 
    integration in Eclipse
    
There have been several 
    posts to this mailing list regarding the usability/integration of Ant in 
    Eclipse. The ANT team would like to acheive a better level of ANT 
    integration. 
An ANT view has 
    been developed by Roscoe Rush (http://freshmeat.net/projects/r2tech-eclipse-antview/?topic_id=46), 
    which is along the lines of integration we would like to achieve. 
    
We believe a user should be able to do 
    these sorts of things: 
* Display one 
    or more Ant scripts in a view which shows the targets, dependencies, and 
    (possibly) tasks, in a hierarchical tree 
* Run a script or selected target(s) from the view 
* Synchronize the Ant view with the associated file, 
    as it is edited 
* Configure the 
    working directory and arguments associated with a script 
* Configure which resources are refreshed after a 
    script is run (if any) 
* Add/order 
    an ant script to be run as part a project's build process 
    
We are currently in the design process, 
    and welcome input from the community. 
Darin