I was actually just going to suggest this pretty soon :)
sure, i'll go ahead and remove all the old struts1 stuff today.
before i do that though i think i want to reorganize the new struts2
code and jsps so that the structure is not so spread out. so for the
actions i would like to take all of them and unify them under a
roller.ui.struts2.* package naming scheme because that just seems more
appropriate and easier to clearly identify all of the code which makes
up the struts2 UI. the second thing i want to do is subdivide all the
authoring actions into subpackages because currently there are about 50
files in that package and it's making it harder to manage IMO.
i assume nobody would care about this since it's not a functional
change, but if you have a better plan then let me know. with this
change i am basically going to leave 3 fundamental pieces to the
roller.ui package ...
ui.core - code which applies to the web ui as a whole
ui.rendering - weblog rendering code
ui.struts2 - the struts2 ui
-- Allen
Anil Gangolli wrote:
+1 to cutting it out. Nice work on the struts2 migration. Let's make a
clean break with struts 1 now.
----- Original Message ----- From: "Dave" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, May 22, 2007 6:45 AM
Subject: Re: ready to switch to struts2?
On 5/16/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
The old struts1 code
will still be left in place and unaltered, so there really isn't much
work to switch back and forth if we needed to.
Is there really any reason to keep that old crap around? It's a
distraction and at this point, we're not going back.
- Dave
