Hello all,

We've released an updated the RichFaces Kitchensink Archetype (version 4.2.3.Final-1), it is currently in a staging repository [1].  RichFaces QE has verified the archetype works as expected, but verification with JBoss tools is still outstanding.

To kick off this final piece of QA, I've created a pull-request updating the JDF stack.yaml file [2], referenced that PR from JDF-151 [3], and created the corresponding JBIDE-13059 [4] issue to verify the behavior when the archetype is invoked from JBoss tools.

Any thoughts on how we can optimize this process? 

One possibility is to create the stacks.yaml PR ask the RF QE team to do an initial verification that the archetype/yaml changes aren't visibly breaking, then at that point hand off the issue to the JBIDE QA team for further verification.

Any other suggestions for improving this process would be appreciated.

Brian Leathem
(RichFaces Project Lead)

[1] https://repository.jboss.org/nexus/content/groups/staging/org/richfaces/archetypes/richfaces-archetype-kitchensink/4.2.3.Final-1/
[2] https://github.com/jboss-jdf/jdf-stack/pull/3
[ 3] https://issues.jboss.org/browse/JDF-151
[4] https://issues.jboss.org/browse/JBIDE-13059