Yeah, I don't entirely get Ales' use case for this either ;-)
:-)
I had Seam or Spring lib/frmwrk in mind, where you probably don't wanna
force the user to use a certain version.
In this case I guess it's different, as you two said, WB compares to EJB,
hence there is no need for multiple co-existing versions.
I can see it would make more sense with some of the Seam 3 modules
where
we aren't enforcing compatibility quite so much.
Yeah, we could see if this makes sense there.