Community
Participate
Working Groups
Build Identifier: 20100617-1415 I wondered why some of my ANT buildfiles in the ANT view suddenly disappeared. The reason is that closing a project in the package explorer _automatically_ also remove the buildfile from the ANT view. (I don't know what this is good for.) But when opening the project again, the buildfile is not added to the ANT view again. Either you disable/make it configurable to remove an entry from the ANT view on closing a project or you make it consistent and also re-add the buildfile when the project is opened again. Reproducible: Always Steps to Reproduce: 1. Create Java Project 2. Add ANT buildfile to the ANT view 3. Close Project in the Package Explorer => entry in ANT view disappears 4. Open Project in the Package Explorer => entry in ANT view keeps disappeared :-(
So what does "closing a project" mean to you? I tend to agree with the IDE that closing means you can't see what's inside. So Ant view has no other choice but removing the now invisible build file from the view. Compare it to editors that are also closed when closing a project. Also the configuration of open editors is not restored when a project is re-opened. Looks consistent to me.
"Consistent" doesn't always mean meaningful/useful! Because of bug #318574 I hade to close one project and open another (toggling between the two projects by closing one and opening the other to work around bug 318574). Can you imagin, how bothersome development is if you have to add the build.xml of your projects to the ANT view over and over again? At least it should be configurable in the ANT view.
First, I'm moving this bug to Platform/Ant where the ant view is implemented. Second, to me the Ant view doesn't seem to be the right place to store your configuration, even just closing the Ant view and re-opening drops all build files. If your workflow heavily depends on using the same build files over and again, have you considered creating "External Tool Configurations" for them?
Our primer is to be able to edit code with a simple text editor and compile/build/deploy projects by calling ANT targets. Of course with this requirement, I reuse this in Eclipse to to create the JARs, ZIPs, DOCs and deploy the projects. So I don't see the necessarity to have to link the ANT projects with the Eclipse open projects.
The Ant View was originally designed like this: the user manually adds/removes build files to/from the view. Closing a project automatically removes the build files. This is an enhancement request to automatically show all build files in the workspace or within a working set, etc. (i.e. some well defined scope).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
