Community
Participate
Working Groups
After running a full maven build, the following message occurs then trying to push changes committed earlier to a git svn cloned repository using 'git svn dcommit'. mgorovoy@glnxlap01:~/code/git/jetty7$ git svn dcommit Cannot dcommit with a dirty index. Commit your changes first, or stash them with `git stash'. at /usr/lib/git-core/git-svn line 499 Running 'git status' indicates clean index, but gitk indicates that the following source file has been updated. mgorovoy@glnxlap01:~/code/git/jetty7$ git svn dcommit Cannot dcommit with a dirty index. Commit your changes first, or stash them with `git stash'. at /usr/lib/git-core/git-svn line 499 Running 'git svn rebase' restores order and allows push to proceed. This ticket has nothing to do with git, it is only to check why a source file is being touch'ed during the maven build.
It would have been helpful if I pasted the file information into the description... Here it goes. mgorovoy@glnxlap01:~/code/git/jetty7$ ls -l jetty-policy/src/test/resources/monitor-test-2/global-all-permission.policy -rw-r--r-- 1 mgorovoy mgorovoy 51 2011-05-13 13:34 jetty-policy/src/test/resources/monitor-test-2/global-all-permission.policy
nothing for us to do with this if your on git, your on your own, nothing we are doing intrinsically that would cause this
This file appears to be touch'ed by PolityMonitorTest. <snip> permFile = MavenTestingUtils.getTestResourceFile("monitor-test-2/global-all-permission.policy"); permFile.setLastModified(System.currentTimeMillis()); </snip> I'll take a closer look how this could be avoided over the weekend. -Michael
Issue is confirmed, working on the fix.
Committed r3146
