Am Mittwoch, 20. Februar 2008 17:16:51 schrieb Brian Pontarelli:
> 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.
My thinking is like this:
upgrading from [today's convention-plugin] to [final convention-plugin]
will be much easier than upgrading from [codebehind] to the [final
convention-plugin].
If convention-plugin is not bundled with the next release, people will stick
to the codebehind plugin. Last time I checked there was no smarturls for
2.1.x as well - so there is really not much choice.
(compiling from the sandbox is no option for most users)
> Furthermore, I think we should all start thinking about when the "true"
> stable release of XWork and Struts2 will be.
Isn't a GA release meant to be a "true stable release"?
I think to know what you want to say, but I am still somewhat confused about
why releases in s2 are working the way they do.
> 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.
I am quite sure there will rise another list with new issues that should be
resolved before a "true" release in some time...
In my oppinion, API stability is nothing that comes with reaching some feature
set or project milestone. This would imply stopping innovation at that point.
For me, API stability needs to be some kind of project goal or philosophy -
which needs to be enforced by defining commonly accepted rules.
But my impression is that this is no (important) goal for s2, and I can hardly
imagine that it will be one day just because it gets to a point where
_today's_ most wanted features are implemented.
But maybe this is worth a new thread...
> 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.
Is it possible to release a 2.1.1 plugin after the core? In this case I do not
feel like it is that important to make it part of the s2.1.1 release :)
Until now I thought that the next possible release for the convention plugin
would be 2.1.2 (or whatever build makes it).
Piero
disclaimer:
I am just a happy convention-plugin user who tries to learn more about s2
development.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
