Page 2 of 2

Re: Issue 118: Bug Reporting inside Forge lacks checks on Re

PostPosted: 24 Aug 2011, 18:40
by Rob Cashwalker
I installed the Windows build of Subversion client, it automatically set the path, and I was able to use the svn command from any folder. But running from eclipse, it was going to exceptions without visible errors. (so I added console println's) I realized that eclipse was still running from before I installed Subversion, so a restart fixed the path error.

Now I finally got the svn rev to show up but I needed to change BuildInfo a bit. It took at least 30 - 40 seconds for svnversion to return, even from a command prompt. While "svnversion src" came back instantly. So I modified the line a bit:(r.9900)
Code: Select all
                String cmd[] = {"svnversion", "src"};
                proc = Runtime.getRuntime().exec(cmd, null, null);

Edit - I just put up r.9901 which fixes all the issues related to the BugzReporter screen and I closed the mantis issues on them.

Re: Issue 118: Bug Reporting inside Forge lacks checks on Re

PostPosted: 24 Aug 2011, 21:42
by Braids
Rob Cashwalker wrote:I installed the Windows build of Subversion client, it automatically set the path, and I was able to use the svn command from any folder. But running from eclipse, it was going to exceptions without visible errors. (so I added console println's) I realized that eclipse was still running from before I installed Subversion, so a restart fixed the path error.

Now I finally got the svn rev to show up but I needed to change BuildInfo a bit. It took at least 30 - 40 seconds for svnversion to return, even from a command prompt. While "svnversion src" came back instantly. So I modified the line a bit:(r.9900)
Code: Select all
                String cmd[] = {"svnversion", "src"};
                proc = Runtime.getRuntime().exec(cmd, null, null);

Edit - I just put up r.9901 which fixes all the issues related to the BugzReporter screen and I closed the mantis issues on them.
OK, that's cool. src is good enough. nice job! =D>

Re: Issue 118: Bug Reporting inside Forge lacks checks on Re

PostPosted: 25 Aug 2011, 02:40
by Braids
Rob Cashwalker wrote:Mind if I remove Git as a potential version?
i'll do that now, but i'm going to create a "detected in Git" tag to replace it first. that way we don't lose history.

edit: i'll go ahead and delete it. i can't search by product version, target version, or fixed in version. :evil:

Re: Issue 118: Bug Reporting inside Forge lacks checks on Re

PostPosted: 25 Aug 2011, 03:11
by Braids
i've copied all the Git Rev Detected and Git Rev Fixed fields into notes, so we won't lose any data. i'll delete the Git custom fields now.
edit: Done.