Community
Participate
Working Groups
I've add in my java project an "external tool builder" task that must be executed after the "Java builder". My task creates a jar with the classes; the task is configured with 'auto-build' than each time I changes a class eclipse creates a new jar. I keep the generated jar under version control (cvs). Each time I tag my project I've a dialog that warns me that there are uncommitted changes even if I've just committed the whole project. The bug is that the commit operation trigs the reexecution of my task and than there is no way to tag my project without the warning. Luckily I can tag the project anyway. Giannandrea
Tagging in CVS unfortunately causes builds to run because the CVS meta files are resources (they are hidden, but resources non the less) and tagging modifies them. So the re-triggering of your build can't be helped. To be a good (efficient) builder you should detect if the changes affect you and require work (in this case, re-writing of the jar). Are you doing this and in this case its not working? That said, it sounds like we are missing a runnable to wrap all our operations so that your build doesn't happen in the middle. We've fixed a bug in this area in the 2.1 branch, so this may now be fixed.
Tagging resources does not modify local resources and therefore does not cause a build. It is committing that causes the build. Unfortunately, if you have the incremental build preference enabled, committing will always cause a build which will always cause an outgoing change. One solution is to turn off the incremental builder (Window>Preferences Worbench/perform build automatically on resource modification). *** This bug has been marked as a duplicate of 25337 ***
