Not quite yet. Currently, jBPM3 is the only engine that the GWT-Console
is integrated with.
We need jbpm33x releases for at least as long as there is no jBPM4
release available that brings gwt-console functionality to the community.
I suppose tomorrows gwt-console meeting will address the issue of how
long the gwt-console will be supported on jbpm3. Generally I agree, that
no more jbpm33 releases are needed if it can be decided that the
gwt-console does not support that bpm engine (any more).
Am eager to hear the outcome of this tomorrow ;-)
-thomas
Tom Baeyens wrote:
the page still talks about 3.3.2 where i thought we were only going
further with 3.2.x.
can we re-org those issues to 3.2.x release and remove the 3.3
releases from jira ?
regards, tom.
Thomas Diesler wrote:
> Hi Folks,
>
> we have Jira Freeze coming up on Monday,12-Jan-2009
>
>
http://www.jboss.org/community/docs/DOC-13217
>
> Could you please finalize the release roadmap for your respective
> components?
>
> cheers
> -thomas
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
BPM Product Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx