Comments for btaz

Comment on GIT Fatal You Have not Concluded Your Merge MERGE_HEAD Exists by michael

michael — Thu, 04 Mar 2010 16:39:57 +0000

Yeah that makes sense. Unfortunately for me even after that it wouldn’t let me commit. I like GIT but there are a few gotchas for sure.

Comment on GIT Fatal You Have not Concluded Your Merge MERGE_HEAD Exists by Will

Will — Wed, 03 Mar 2010 00:58:48 +0000

It wouldn’t let me commit either until I did a git add on the file I had to manually merge.

Comment on GIT Fatal You Have not Concluded Your Merge MERGE_HEAD Exists by michael

michael — Tue, 02 Mar 2010 19:42:34 +0000

That’s interesting and I’m glad it worked for you. In my case it wouldn’t even let me commit.

Comment on GIT Fatal You Have not Concluded Your Merge MERGE_HEAD Exists by Evan

Evan — Tue, 02 Mar 2010 04:18:00 +0000

FYI, for anyone else who stumbles across this page like I did (by searching that error message): All I needed to do was commit.

Comment on What jar file does a Java class belong to? by Ed

Ed — Fri, 13 Nov 2009 04:44:56 +0000

If you’re developing with maven and need to find classes (currently 8 million of them) in the central repository, the maven repository search engine at http://www.jarvana.com can be very useful, since it provides the dependency information for the class/artifact that you’re looking for.

Comment on JUnit 4 error: reference to assertEquals is ambiguous by Duran

Duran — Tue, 22 Sep 2009 12:29:12 +0000

Finally I have found what I think is the problem. With Eclipse, the delivered JUnit 4.5.0 jar doesn’t behave as the 4.3 version. If I ecplicitly points to the version I have downloaded from JUint.org (a new 4.7 version, not polluted by Eclipse) it works again

Comment on JUnit 4 error: reference to assertEquals is ambiguous by Duran

Duran — Tue, 22 Sep 2009 11:33:03 +0000

I have a similar problem but I haven’t come up with a solution yet. This code doesn’t behave as expected with JUnit4_4.5.0:

assertEquals(“Always fail: “, 0L, 0L);
assertEquals(“Always OK: “, Long.valueOf(0L), Long.valueOf(0L));

I haven’t figured out why, and haven’t come up with an acceptable solution either since similar code exists in numerous test cases.

Comment on JUnit 4 error: reference to assertEquals is ambiguous by Virginia

Virginia — Wed, 09 Sep 2009 18:57:57 +0000

Thank you, thank you. I encountered this problem when I upgraded my JUnit4_4.3.1 to JUnit4_4.5.0. Using the older version, I was comparing “double” to “Double” and the assertEquals(Object, Object) method worked fine. After the upgrade, I received the error you describe above. Your post was very helpful.

~ Va