Wouldn’t it be nice if you were able to write
@Getter @Setter private int age = 10;
which would generate those boilerplate setters and getters into the compiled code without messing up your source code?
With Lombok you get this and some other cool features most Java developers have on their wish list – and without setup hassle!
How to find a concurrency bug – this was the question I asked myself some time ago.
It is always very hard to find a concurrency bug. Mostly you have no idea when it happens or if it is really a concurrency issue or some nasty bit of code. If it is a concurrency issue the question is if the bug is in your code or in a supplied library? Will the problem happen only on multicore processors or on any machine? Besides the technical problem the customer is eager to get a solution and management… we’ll i guess you know the story.
I won’t be able to tell you everything there is to know about concurrency testing – but I’ll show you a way that worked for me in most cases.
Have you ever used your own custom ant task in the eclipse environment. Well – I have written some ant tasks and they are being used by all developers in our company. But there’s the annoying thing that I always have to add the libs containing my tasks to the classpath. Nothing easier than this you might be thinking. Add it to ants classpath in the eclipse preferences. This works on my machine but what about all other developers? What about updates to the libs?
I guess I found the perfect solution for this problem. Write an eclipse plug-in that adds all libraries to ants classpath using the extension point of the ant plug-in and put the plug-in on an eclipse site so all developers can get it automatically.
That’s easy to say but how? Lets get our hands dirty…