I don't think it's related to the pull workflow per se.
The recommendation is to almost always add a JIRA issue number to a given
commit unless you fix a minor type or such. That way every commit has an
associated JIRA and hopefully the git/jira link holds.
On top of that, for Hibernate Search.
Hello,
In the quest to write a proper unit test for HSEARCH-625 this night
I've introduced Byteman
in the testsuite of Hibernate Search.
I must say I'm impressed and love the tool, the fix is ready and the
test rocks, it empowered me to
write code with confidence to catch the IOException errors in
+1 for Byteman
Anything which makes testing easier sounds good and I've heard before that
Byteman makes
it easier to test border/exception cases.
--Hardy
On Thu, 09 Dec 2010 10:45:04 +0100, Sanne Grinovero
wrote:
> Hello,
> In the quest to write a proper unit test for HSEARCH-625 this nigh
Ok,
enabling it as HSEARCH-644 so we can keep the change separate from HSEARCH-625.
Sanne
2010/12/9 Hardy Ferentschik :
> +1 for Byteman
>
> Anything which makes testing easier sounds good and I've heard before that
> Byteman makes
> it easier to test border/exception cases.
>
> --Hardy
>
> On Th
We plan to go GA next Tuesday, so now is the time to test.
Some heavy @IndexedEmbedded users will be pleased with the performance
improvements. We also have an Infinispan-stored Lucene directory provider.
See the full blog entry at http://goo.gl/HNz1r
Emmanuel
__
