Lóránd Somogyi

We use Maven2 for developing our huge application, (and few smaller). We have almost 200 projects which depends on each other somehow. That’s why I really like Maven2. It was a nightmare to handle all those dependencies by hand, – as we did it before moving to Maven. Of course there are other great things about Maven, like reports, site and of course the release management. – OK, there is still an annoying bug with release plugin, ranges and snapshots, but we can live with it.

With the release of 2.0.9, we got a new powerful feature for handling dependency versions. The so called “Importing Dependencies” noted in release notes and described in the documentation and in wiki.

Read more…

Lots of software companies does not Open Source their software. It is a bad practice, and a waste of money. Open Souring your software has a real good ROI.

This article is first of all for business people leading software companies, or for those who pay for software development. Actually for all those who are decision makers. On the other side I hope it will be interesting for software architects, developers too.

This is not mean to be an in-depth analysis or an article about sheer numbers, charts and stuff. It’s just few thoughts and examples from the real world.

Read more…

We use Continuum 1.1 as our Continuous Integration server. We also have an LDAP directory that we like to use whenever it comes to user management. So we tried to integrate Continuum with LDAP. As described by the documentation, and here we configured the Continuum to use LDAP authentication.

Everything looked fine. Users could log in, as expected.

But there was one nasty problem. When we tried to change user roles, the users were not in the users list. Even if they logged in, the list showed only the admin and the guest user (and one user created before the LDAP configuration). We tried to google for an answer, but no luck. We tried to tweak the configuration, but it did not worked…

Read more…

This is a short guide on how to install Munin (actually munin-node) on Sun Solaris 10. I installed it on x86, but is should work on other architectures too…

Read more…

I was playing a bit with Hibernate and Groovy. I was about to examine the possibility of using Groovy producing JPA Entities.

As I use Maven 2, the natural way is to create a project and define dependencies. As a good Maven user I was looking for the best artifact in the maven repository. I found Hibernate, and Groovy too. I took the latest from both. For groovy there was a choice between groovy-all and groovy. The groovy POM file was more descriptive, so I took that one.

Now that was a bad idea.

The problem is: Hibernate depends on ASM 1.5.3 while Groovy depends on ASM 2.2. ASM is not backward compatible, so ASM 2.2 won’t work for Hibernate. It will fail with class not found exception, (and vice versa for Groovy). After a day of hacking Maven POM file, and looking for some solution, I found this. Just look at the last paragraph, there is the solution. Just pick groovy-all. So I did that, and everything is fine again. Or at least to thought so…
I work on a framework, so I need to use ASM to enhance or to create some code at runtime. I usually do that by using ASM Eclipse plugin, because that is the fastest and easiest path. But that plugin relies on ASM 2.2, and now I’m back where I was…

Ok, I could use a class loader hierarchy, but that would mean special configuration for Maven, or even worst, special configuration at deployment.

I think the Hibernate team should consider the solution Groovy team made.

Or I’m going to do that.

Nice and easy.