On 9/24/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
Don, "compat" is much better. The problem, as I see it, is that you will then have to be supporting the "compat" package as Struts 1.x continues to be upgraded.
I agree that "compat" is closer to the right sentiment, but I think "integration" would be spot-on for the top level folder. Since we may also want to do this with other similar codebases, like Spring MVC, we should be more specific with the lower-level package name. For now, I changed the folder to "integration" and the package to "s1". - /current/struts2/legacy + /current/struts2/integration - package org.apache.struts2.legacy; + package org.apache.struts2.s1; In the past, we used "legacy" to remove software that the PMC has decided not to support, for lack of interest (namely our datasoruce). That is clearly not the case with Struts 1. We might want to consider putting these and any other integration classes into the extras module.
How can you provide a "compat" module for a moving target?
By waiting until it stops moving :) I would venture that we would write integration classes against the lastest GA release, or perhaps the most popular GA release, or whichever GA release volunteers working the code wanted to support. In the case of Struts 1, in my experience, the most popular GA release is still 1.1, not the head. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
