After re-reading this thread from scratch, I've got a few comments. Yes... this scenerio *will not* *ever* work. The archives model is updated by the builder, which passes in changed workspace resources since the last build. Deleting files from the deploy folder will not trigger any resource change events and the builder will not alert archives as to the changes. This is not a supported use case and I doubt it ever will be. Again, in this case, the workspace / archives is not aware of what's changed in the deploy folder. It's only aware of what changes in the workspace. Just as deleting class files from the deploy folder will not trigger resource change events, neither will deleting a project from the deploy folder. Publish and republish are both incremental publishes. They're incremental from the point of the workspace and source files, *not* from the point of the server / destination folder or module. The tools cannot verify whether the workspace has changed when you were outside of eclipse. For this reason, upon startup, unless "build automatically" is not enabled, the model will rebuild that jar. The reason for this is fairly obvious. If, for example, you deleted the destination jar when eclipse was not loaded, and then you start eclipse, and change one or two files, only those one or two changed files will be in the jar. If build automatically is enabled, upon starting the workspace, View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218870#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...