Re: [jdf-dev] Quickstart Organisation (was Re: Quickstart for how to inject Spring into Java EE)
On 12 Jul 2012, at 19:07, StevenBoscarine wrote:
Well, even if the plugin is half-baked does that change the
quickstart? The quickstart is "This is how you inject a Spring bean into a Java EE
resource."
We try to only show fully supported (both project and product, see
www.jboss.org/jdf/about/roadmap) things in the quickstarts and tutorials. We also want to
make sure we don't "bait-and-switch" on users.
seam-spring is not supported, and never will be. However DeltaSpike is planned to be, and
will include a spring integration module. However, not yet (again see the roadmap for then
this will arrive).
Hence the proposal that we don't hold up development of quickstarts, but also indicate
to users that this an "experimental" feature for now.
Whether it's through seam-spring or some new plugin that gets rewritten, does it
matter?
I imagine RedHat would want to simply keep the same principles and update the Quickstart
whenever the current seam-spring plugin's successor is completed.
On 7/12/2012 12:08 PM, Jason Porter wrote:
> I'm completely fine having them in the larger QS repo, I simply didn't want
to put anything half baked in there when I started, also since we won't have DS in jdf
for a few more months, this gives us some time get an app in place and create some greate
quickstarts from it for DS and a decent testsuite for said app.