Sounds like a good start. There is interest from the Apache Maven team to host the general purpose Maven plugin work we have done, especially the Maven JDeveloper plugin to generate a JDeveloper workspace and projects for multi-module Maven projects.
What is the most appropriate way to proceed? I'm trying to adopt the "Apache Way" here. :-) tc, -john. On 4/13/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 > -- http://apress.com/book/bookDisplay.html?bID=10044 Author: Pro JSF and Ajax: Building Rich Internet Components, Apress
