Oh, I see what you mean. Sure, why support something you already have a
replacement for? Just take it out of the build and move them to an "extras"
distribution for others to get -- they should no longer come as part of the
standard distribution.

BTW... Right now, the plugins are part of S2 release. I think if the
plugins could be independently developed and released like Maven plugins,
you would have no problem doing this. I was once against this approach
because it would be difficult to find which core and plugins were releted,
but I would like to reconsider this. Therefore, push S3 plugins into
"org.apache.struts.plugins" groupId and let them develop their own
lifecycle.



On Mon, Mar 18, 2013 at 1:33 PM, Lukasz Lenart <[email protected]>wrote:

> 2013/3/18 Paul Benedict <[email protected]>:
> > Ah, that wouldn't be nice to Struts 2 users :-) Just let Struts 2 be as
> it
> > is. Perhaps add notes to the documentation and call it quits for those
> > plugins.
>
> Yes I know, but with S2 versioning policy in place it should be
> already S4. What I mean is that the plugin will support already
> unsupported technology. Also the Zero Configuration and Code Behind
> plugins are already covered by the Convention plugin. The Dojo plugin
> is the same death as S1 - it isn't possible to support without
> rewriting it from scratch.
>
> Just to understand my concerns, please take look on the versioning
> scheme right now: [2].major.minor/patch.security.
> Someone has already pointed out me that the S2.3.12 introduces some
> backward compatibility breaking changes, but with such versioning
> policy is very hard to handle changes smoothly.
>
> That's why I would like to drop support for these plugins - we can
> even call it S2.5 to clear say what kind of changes represents that
> version.
>
>
> Regards
> --
> Ɓukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to