Imagine that you are a Java developer, and you’re about to start your next big project. You need to make the fundamental decisions that will stick with you for the rest of the project. You want to pick the best object-oriented abstraction of your flexible data model because you do not want to deal with plain SQL. You want to support all kinds of data, and ideally, support all sorts of databases.
I was honored to speak about Hibernate at great SJUG (Silesia Java User Group). Below you can find some resources and useful links about group and the presentation.
Yesterday I was honored to speak about static code analysis on in the great SJUG (Silesia Java User Group). I was talking about static code analysis and the audience was great :). Thank you!
Final release (version 1.0) is available to download. This ends series of articles and delivers complete software product. I would like to summarize last few months here. What has been done and achieved during the lifetime of the project so far.
The final step before the release is to cleanup the test code. Some test cases are really too complex and I want to make them more clear and straightforward. Simpler tests are making adding new features less error prone and more straightforward.
We haven’t changed the logic and still have the same code to use. This way we’ve separated behaviour and definition of cleaning from the logic of cleaning itself. It’s very clear and easy to add new definitions.
In previous post we’ve significantly reduced amount of code. Now let’s try to push it further.
In previous post we’ve removed dependency. Now let’s try to use some Java 8 sugar.
I was planning to implement support for few new frameworks out of the box. This way some projects will be discovered by default. No need for custom configuration. That is the main purpose of the tool. I’ve implemented Grails 2.x support but it turns out that I have to write down lots of code in order to implement another cleaning definition. That was the perfect moment to small refactor as I knew what kind of usage would be most suitable for me.
In unit tests of ot-clean, I’m using only MatcherAssert for matching purposes. Why?