First of all! Thanks for a great plugin. I really love it!

I'm now trying to setup our build system with the new stuff in the Ivy Project type which can build at module level, which is by the way GREAT!

Let me describe the issue i have.

I sat the svn directory to http://subversion.com/myproject/

myproject has subfolders for example
trunk
branches/1.0
branches/1.0.1

I'v also attached the jpg to the view. My goal is to be able to run older releases (branches catalogs) with the current main line (trunk).
This works fine in the sentense that hudson does trigger the correct version regarding the version number (which it didnt in a freestyle job).

But its really hard to tell in the view above which of the modules which belong to which catalog?
I think it would be nice if you could choose to view the path at the view for instance MPP.Clients.SilverlightPlayer (trunk), MPP.Clients.SilverlightPlayer (branches/1.0.1)

Or if you have another way to solve this i would love to hear it!
It would be great if we could use one build server instead of multiple. Or is the idea that you should dedicate one hudson instance per building type, release, mainline?

Thanks alot again! Love your work!