Putting aside all the "(why) should we do this" discussions for a moment...
Let's assume that the community around a particular J-C component, say commons-foo, decides that it wants to move to A-C. Would there be - or perhaps, should there be - any rules about what commons-foo can depend on, once it has moved to A-C? Is it OK for an A-C component to depend on a Jakarta project? How about a(nother) J-C component? Apart from my own edification with respect to the intended boundaries and scope of A-C, the answers to these questions may provide a filter to help us determine potential candidates for "early adopters", if you will. For example, commons-math has been suggested as a potential candidate for moving to A-C. However, commons-math has dependecies on five other J-C components. Would that be OK, or would those components need to move to A-C first? (BTW, I'm not involved with comons-math, nor am I suggesting one way or the other whether it should move. I merely use it for the purposes of illustration.) -- Martin Cooper
