My plan is to bundle Action 1 with Action 2 for distribution, and in
fact, the Action 2 build will depend on Action 1 already for the
migration library. The Action 2 classes are in a different package,
which should help them run side by side. I'm hoping to take it further
than make it possible to share messages and things like validation
configuration files between the two. We'll see how that pans out, however.
To clarify, Action 2 will not _merge_ with Action1 so they will remain
their own branch, build, etc., so I'm talking about the Action 2
distribution file including Action 1 jars.
Don
Paul Benedict wrote:
The Action 1 migration is probably the
most important part of Action 2, at least in the beginning. We need to
make it easy and obvious for developers to move.
Don, is Action2 going to include ALL the classes from Struts
1.3 (same package name) so that I can run action2 and action1
in one framework? Or is the plan to tell developers to run two frameworks
in one application?
Paul
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
