The analogy doesn't apply to HornetQ here. You could make the analogy to JBoss.
JBoss AS still alive.
JBoss Messaging isn't a very creative name... it denotes more a sub-project of JBoss (What JBoss Messaging seemed more like).
From the point of view of "JBoss", this is maybe not a very creative name, but it's a clear name nevertheless ;)
HornetQ can run embedded, standalone... and inside the application server as well.
I understand this. For the end user, this is a blessing and a curse at the same time. It's a blessing since this assures that you apply ace engineering principles by having the "messaging module" of JBoss AS among others completely honor separation of concerns. It means JBoss AS is a modern, modular thing, and not a monolithic beast that the old J2EE servers were. This is obvious a Good Thing.
It's a little bit a curse, since I'm using JBoss AS. Our clients are using JBoss AS. We have a problem with JMS in JBoss AS. Where do we go to? The general JBoss AS forum directs us to "some JMS forum". But what is "some JMS forum"??? Is it ActiveMQ? Is it JBoss Messaging? Is it HornetQ? Why does JBoss AS have 3 messaging forums? Which one is really is concerned with just JMS anyway? Let's try JBoss Messaging... hmmm no response at all. Let's try HornetQ? Hmmpph... we're turned away since it's a JMS question, and JMS is JBoss AS and HornetQ is about general messaging. But what is the difference between "general messaging" and JMS? Let's try ActiveMQ then... still no dice... now I'm directed to a forum about "remoting"??? What is the "remoting" forum???
This can go on and on.
It would be helpful if there was at least a view of the support forums and project pages with JBoss AS as the root and then all projects it consisted of as children. This would undoubtedly upset you guys, since I know you are very proud on your "core API", which is a standalone thing and not related to JBoss AS, but remember this would just be -a- view. You could provide a second view which organized the same projects differently, i.e. such that HornetQ was as far as possible away from JBoss Messaging and JBoss AS :P
You could have this JBoss AS centric view like this:
ActiveMQ (JBoss AS 4.x)
JBoss Messaging (JBoss AS 5.x)
HornetQ (Jboss AS 6)
I respect your opinion though. However the majority seems to have understood the change.
Of course I respect your opinions a lot too, and it may make sense to periodically rename the project when some major milestones are reached (maybe Sun should have did this with EJB3 too), but I just wanted to let you guys know it can be confusing too.