If we do not have different package names, we cannot run both Struts 1 and
Struts 2 in the same web application. So it's very important to encode the
version into the pacakge structure. Otherwise, the migration path to Struts 2
is all or none. This is not a unique idea; this has been espoused by other
committers.
Dakota Jack <[EMAIL PROTECTED]> wrote: Give it up! Lord! What nonsense. Do
you hate versioning, Paul?
On 6/28/06, Paul Benedict
wrote:
>
> I am guessing the winner is going to be struts1/struts2
>
> So if struts1 is:
> org.apache.struts
>
> If struts2:
> org.apache.struts2
>
> ?
>
> Niall Pemberton wrote: On 6/29/06, Don
> Brown wrote:
> >
> > I like struts1/struts2.
>
> +1
>
> Niall
>
> > Don
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Next-gen email? Have it all with the all-new Yahoo! Mail Beta.
>
--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~
---------------------------------
Sneak preview the all-new Yahoo.com. It's not radically different. Just
radically better.
