Hi Claus,
thanks for applying those 2 changes as well...
While I was looking into the conversation we had in this thread, I suddenly
realized that I misunderstood your answer completely regarding unit-tests,
that's the following answer of yours:
> For unit tests I doubt it have any effect, as the unit test is short
> lived and executed once when testing. In camel-core it could be
> another matter as that code is what you run in production.
Which I thought it has to do with the following question of mine:
> Another question I have is regarding the patch I provided by [2]. Just
> wonder why you didn't want to take over the 2 changes with
> assertTrue(file.delete()) stuff in TestSupport:
> // assert on the return value below so that we surely know that
> the file has been deleted
> // as it could be that some native processes're sitting on the
> file prohibiting the deletion
> // (i.e. on windows that could be the windows explorer, etc.)
> assertTrue(file.delete());
> Or maybe even better:
> assertTrue("deletion of " + file.getAbsolutePath() + " failed!",
> file.delete());
Just wonder what you really think about this change which was not taken over
in Subversion Commits for https://issues.apache.org/jira/browse/CAMEL-4255
In my case it was really vital, see my previous reply with HSQL stuff. I
just want to make it sure that it was not your IDE rejecting that change, as
it apparently happened with the last patch.
Regards, Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Favor-static-member-classes-over-nonstatic-tp4634964p4639321.html
Sent from the Camel - Users mailing list archive at Nabble.com.
