Community
Participate
Working Groups
Build ID: M20070212-1330 Steps To Reproduce: 1. use the following ant-file <?xml version="1.0" encoding="UTF-8"?> <project name="Test" default="printmodified" basedir="."> <!-- Includes all source files --> <fileset dir="." id="files"> <include name="src/**/*.java" /> <modified /> </fileset> <!-- Print modified files --> <target name="printmodified"> <property name="myfiles" refid="files" /> <echo message="Files = ${myfiles}" /> </target> <!-- Delete modified information --> <target name="clean"> <delete file="cache.properties" /> </target> </project> 2. Exceute it on a Java project with at least one java source file in src 3. Call the target "printmodified" by right clicking on build.xml, run as ... ant build: First it should print all source files and on the second call it should print no files. 4. Step three can be reproduced after calling clean target 5. Drag the build.xml to ant view, and execute the printmodified target: The target does not echo any files The problem is that dragging a build.xml to the ant view evaluates the filesets in the file which confuses <modified/> option of the filesets. More information:
Moving to Platform/Ant
Are there any updates to this issue? It seems to me that the evaluation of the <modified /> cache file still occurs when I drag and drop the build.xml to the ant view. May this behavior be intended for some reason? The issue with this (or the issue for me at least) is that it may break incremental builds and forces us to clean projects from time to time. This is because a frequent sequence of steps is - first to apply some changes to the project - then open the buildfile in the Ant view - and then run the build (which does not detect any modified files).
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.
