On 3/24/06, Don Brown <[EMAIL PROTECTED]> wrote: > > Ok, after listening to all the feedback, here is my revised renaming > strategy proposal: > > - com.opensymphony.webwork package -> org.apache.struts.ti > - WebWork* classes -> Struts* > - WebWork in comments, documentation -> Struts Action 2 > - webwork. as the configuration properties prefix -> struts. > - ww: tag prefix -> a:
That works for me. Or af or saf instead of ti. I'm not a fan of having version numbers in package names, though. -- Martin Cooper Since Ti is the code name for Action 2 and there is significant > precident within Apache for naming next gen code using a code name, I'm > proposing the org.apache.struts.ti package. Besides, our JavaOne > session is called "What's up with Struts Ti?', so I guess we're stuck > with it. :) I'm kinda against 'saf', as I get my fill of acronyms from > my day job (US DoD) :) > > I'd like to get this resolved quickly, so I can start the massive > renaming work this weekend. Thanks for all the good feedback so far, > > Don > > Don Brown wrote: > > I've renamed the WebWork packages, and both the code compiles and all > > tests pass correctly. However, as I start with the greater renaming > > task, I thought I'd propose a strategy and get some feedback on it: > > > > - WebWork* classes -> Action2* classes > > - WebWork in comments and documentation -> Struts Action 2 > > - webwork in comments, documentation, and as a properties prefix -> > > action2 > > - ww: tag prefix -> a2 > > > > What does everyone think? Did I miss anything? I know the '2' seems > > unnecessary, but it does match our package name > > (org.apache.struts.action2), which is necessary so that Action 2 and > > Action 1 apps can live side-by-side. > > > > Don > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
