Already done the package renaming? If not, what about having one more additional namespace level: org.apache.myfaces.adf.api org.apache.myfaces.adf.internal (or impl? - which sounds more common to me) org.apache.myfaces.adf.build org.apache.myfaces.adf.demo
I think this would separate things even more clearly: All ADF stuff in one "master" package. But that's just my 2 cents. Never mind if renaming is already done. Manfred On 4/14/06, Adam Winer <[EMAIL PROTECTED]> wrote: > > While I'm waiting for a clear spot to start checking in, > we can talk to resolve some basic issues up front. > > First up is a package name. There's no requirement for > any final decision until we leave incubator, but I'd like > something better than "oracle.Anything" for the first > checkin. > > Does "org.apache.myfaces.adf" sound reasonable? > And "org.apache.myfaces.adfinternal" for all of our > internal code? ADF Faces uses package partitioning for > solidified public APIs vs. internal private APIs, and > I'd like to continue that here. > > And, FWIW, "org.apache.myfaces.adfbuild" and > "org.apache.myfaces.adfdemo" for our build tools > and demo code. > > This'd also carry over to constants, init params, component > families, renderer types, etc. > > -- Adam >
