Hi folks,
I've been looking again at the Stripes Extensions landscape a bit, and I
found it a bit messy. And I'd like to reopen the debate that started on
LinkedIn some time ago about the "pluginification" of Stripes. And not only
reopen the debate, but actually do something !
I'm in favor of moving the well-known extensions (StripesStuff, Stripersist
etc) into our 1.5.x branch as submodules, benefiting from our infrastructure
(continuous build, jira, maven deployment, wiki, ...). Right now.
For extension developers, it's just about cheking the sources in the stripes
svn (and possibly create/adapt the maven build of the extension to make it
fit with Stripes').
For extension users, information would be centralized (no need to struggle
in order to find what you need), and the plugin would be very easy to
include (a <dependency/> in the pom).
Of course the extensions will still be separate, and optional : stripes.jar
is left as is. What I'm thinking about is just to make the "community
approved" extensions available from a single source.
If any help is needed, I'm offering mine.
We could probably start by Stripersist or StripesSecurity, which have been
around for a long time. I've just looked at the code in Stripersist, and I
think it's really easy to mavenize.
So ? Sounds reasonable ?
Cheers
Remi
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
