Adam Winer 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.
+1 It would be strange to keep the Oracle package name although it can
be changed later. The sooner we can come up with a new "name" for this
project the better for everyone, but for now this is fine by me.
And, FWIW, "org.apache.myfaces.adfbuild" and
"org.apache.myfaces.adfdemo" for our build tools
and demo code.
+ 1
This'd also carry over to constants, init params, component
families, renderer types, etc.
-- Adam
- Jonas
--
*Author*: Pro JSF and Ajax: Building Rich Internet Components
<http://apress.com/book/bookDisplay.html?bID=10044>
*Blog*: http://www.orablogs.com/jjacobi
