On 3/17/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > Any thoughts on grouping the Action 1 related modules together in some way?
Hmmm, that's going to depend on what you mean by Action 1 related modules. Would Scripting and Flow fall into that category, or just Action, Apps, EL, Extras, and Taglib? What about Tiles when it comes up from the sandbox? It looks like that can be shared by all three frameworks, Action, Action2, and Shale. > And where do you see the WW/Action 2 code being added, when it comes > out of the incubator? (Does 1.3 become a branch, or is action2 a > separate trunk?) My suggestion would be to treat the codebase the same way we are handling Shale, except the root package might be something like org.apache.action2 or org.apache.struts.action2. In the sandbox, I started an "action2" folder and added "apps" under that. I've got a good start on an Action 2 Cookbook, and an Action 2 Mailreader is next. Here I'm using package names like cookbook2 and mailreader2. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
