The API has yet to be solidified and there are a few things that I'd still like to discuss and possibly change in that regard. My main goal is to ensure backwards compatibility in the convention plugin API. Furthermore, I think we should all start thinking about when the "true" stable release of XWork and Struts2 will be. I think it makes sense to target the next release and jump up to 2.5 or some number to indicate stable APIs. This would include a number of API clean-ups, OGNL replacement and a few other things that will severely break plugins and applications. After that release, API changes should be compatible so that plugins and applications can be upgraded without requiring re-compiling.

Back to the convention plugin...

If folks would like to discuss the API and solidify it over the next few days, I'd be up for that. I'll start a new thread for that and we can hopefully get things ready for a 2.1.1 final release of the plugin shortly after the release of core.

-bp



Piero Sartini wrote:
I think you should release the convention plugin at all costs - but this is just a vote from an user.
        
        piero

Am Montag, 18. Februar 2008 18:16:52 schrieb Brian Pontarelli:
Don Brown wrote:
I've cleared all but a couple issues out of Struts 2.1.1, so I think
we are ready for a release.  The only kinda blocking issue is the
portlet tests failing, but that seems to have something to do with the
setup, not our portlet code, so we could even punt that one.

Any objections to rolling a release(*) in the next day or so?
Shall we queue up the convention plugin addition and deprecation of the
smarturls and code-behind plugins for next release than?

-bp


---------------------------------------------------------------------
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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to