It's not "administatively forcing a separation", it's a natural consequence of a particular group of components growing up together and "graduating" with a common purpose. The HttpClient component grew into the Jakarta HTTP Components subproject, and the Jakarta Web Components subproject will likelyabsorb some Commons components as well. What makes it wrong, or evendifferent, for a group of Java-language-focussed components to "graduate" into Jakarta Language Components? To me, it's simply a natural evolution ofthe community.
...on the other hand it might hard to decide whether some belongs to that grouping or not. The definition of "language focussed" is just too blurry IMO.
What about tagging the components? :-P cheers -- Torsten
smime.p7s
Description: S/MIME cryptographic signature
