This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am at pretty early days with using Eclipse 3.x - I am more a vi veteran when it comes to coding. Also I am pretty new to using ant for automation of builds having come from a shop which used make to build native code alongside Java.
So here is my query. I can see the benefits of integrating ant into the Eclipse IDE but how well integrated is it at this point in time ? Before I've even gone to the trouble of setting up an ant build.xml and managing it from within the Eclipse IDE it occurs to me that there might be a potential for duplication of information such as build paths stored within the IDE (this gets munged into the .classpath file, right?) and build path info wired into Ant. So, do folks typically run ant alongside the automated build capabilities offered by the JDT eclipse environment and duplicate info or are the build path details kept in sync via some sharing mechanism.
I know I can dive in and see but firstly I wanted to get a grip as to how people are typically integrating their use of ant into the Eclipse IDE and whether duplication of config and maintenance of config is an issue when using ant alongside the JDTs own build facilities.
Thank you for the useful replies about Eclipse/Ant integration and how you folks use it in practice. Now I need to beef up on learning to use ant itself. Time for a coffee and read of the ant manual and probably some sample build.xml scripts to get me bootstrapped.
thanks for a kind and helpful response to my first JavaRanch query.