malabar-test-class-buffer-p isn't good enough
Reported by Espen Wiborg | February 27th, 2009 @ 10:00 PM
It fails in the case of a test-supporting class (such as a fake object).
Determining the classpath needs to take file location into account as well.
Comments and changes to this ticket
-
Espen Wiborg March 4th, 2009 @ 04:03 PM
- State changed from “new” to “resolved”
(from [f6ba0db75c5a8bd584887e579c586973d180afc1]) Apply test classpath based on file location, not buffer contents. [#27 state:resolved] http://github.com/espenhw/malaba...
-
Espen Wiborg March 5th, 2009 @ 01:51 AM
- Milestone cleared.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
A better Java mode for Emacs
People watching this ticket
Espen Wiborg
Referenced by
-
27
malabar-test-class-buffer-p isn't good enough
(from [f6ba0db75c5a8bd584887e579c586973d180afc1]) Apply t...