> > It does feel like jumping through hoops though to fix earlier > > mistakes. Therefor I still think Jakarta Commons should fix their > > naming scheme. But that will have to be brought up there, not here. > > It's a Jakarta naming scheme and not a Jakarta Commons one > afaik. No jakarta projects include jakarta in their naming scheme. > > I imagine the reasons are: > > 1) Legacy. org.apache.java became Jakarta. > 2) Ownership. This underlines that Apache own the code and > not Jakarta. > > But you'd have to find some aging old-timer from the early > days to give you the 'when I was in the war' story. >
Having been a lurker in the war :), the reason was that Jserv started that way, and *EVERYTHING* copied that as a way. It was assumed that there would be one java community in apache, so org.apache.* was determined to be easier to type. (Little did everyone know that there would be 4). Scott
