[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-1402) archiving does not run after rename/add/delete file

[ http://jira.jboss.com/jira/browse/JBIDE-1402?page=all ] Rob Stryker resolved JBIDE-1402. -------------------------------- Fix Version/s: 2.0.0.GA (was: 2.0.1) (was: 2.1) Resolution: Cannot Reproduce Bug Assignee: Rob Stryker unrepeatable so far. Seeking more information. My breakpoint is set at ArchivesBuilder line 74. I have a simple have a simple java project with a few src java files and a txt file. I have an archive structure where the generated jar looks like the following: |- SomeProj222.jar |- ABC |- some.txt *** here is the file to be renamed |- .classpath |- .project |- .packages |- bin |- A.class |- B.class |- src |- B.java |- A.java I rename the some.txt resource to nyt.txt33. IMMEDIATELY thereafter, the builder is called. I traced forward two steps. if (kind == IncrementalProjectBuilder.INCREMENTAL_BUILD || kind == IncrementalProjectBuilder.AUTO_BUILD) { fillDeltas(interestingProjects, addedChanged, removed); addedChanged includes nyt.txt33 removed includes some.txt. The files are appropriately changed. A deep-search of the jar immediately afterwards looks as follows: |- SomeProj222.jar |- ABC |- nyt.txt33 *** here is the file as changed |- .classpath |- .project |- .packages |- bin |- A.class |- B.class |- src |- B.java |- A.java The same is true after renaming A.java. This issue is unrepeatable. Please verify. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira