Chris,
Thanks for the link! I'll be sure to follow that convention from now on. I
should have been paying closer attention to everyone else's commit messages
because it looks like I'm the only one who's been putting the ticket number
after the message. Would anyone be against placing the link on
I tried using git bisect (for the second time) to tackle this issue and ran
into an interesting issue. git bisect took me from master to 1.4. This
was unexpected at first, but I understand why git is doing this. I would
like to avoid this and only consider commits in master.
$ grep -A 5
With risk of making this more complicated- I just noticed that the first
commit posted was still broken- though it didn't lock up like the version
currently in master, it appeared to run but threw the ClassNotFound
exception in the Main.err log.
I'm still poking at this as well.
On Tue, Oct 8,
On Tue, Oct 8, 2013 at 10:06 PM, Corey Nolet cjno...@gmail.com wrote:
With risk of making this more complicated- I just noticed that the first
commit posted was still broken- though it didn't lock up like the version
currently in master, it appeared to run but threw the ClassNotFound
I had started my bisect at the first commit at which it was introduced,
though it looks like it still took me on a similar path as where it took
you- needless to say, after the 9 or so steps that it allowed me to take,
the minicuster command was still broken.
On Tue, Oct 8, 2013 at 10:12 PM,
