This Drools upgrade, and a probable upgrade to jBPM 4 (happening due
to these products needed in the JBoss SOA platform 5, based on EAP 5,
which in turn includes Seam) mean that we need to make the release
Seam 2.2 (which I said would never happen, I know ;-)
Due to the concentration on Web Beans / Seam 3 there hasn't been a
huge amount of activity recently, however 2.2 will include:
* 112 issues closed (please direct your thanks to Norman here - he has
been soldiering away!)
* improvements to Seam-gen (Glassfish, IDEA etc.) from Dan
* big improvements to REST support - Christian and Jozef
* Drools and jBPM upgrades
So, I suggest that Norman and Marek (can you coordinate with each
other) handle the jBPM upgrade (Tom just released alpha2, and plans
the GA in the mid summer) - we should wait until there is a beta out I
think for Seam 2.2 GA... Tom, any rough guess when this will be?
Assuming Tom has a beta, I propose this schedule:
Seam 2.2.0 CR1 - Wednesday 22nd April
Seam 2.2.0 - Wednesday 13th May
Seam 2.2.1 CR1 - Wednesday 17th June
Seam 2.2.1 - Wednesday 8th July (hopefully just after the jBPM GA)
This will be the first time for time-boxing our releases too,
something we are doing for Web Beans, and will do for Seam3.
Anne-Louise, could you please comment on how these dates fit with EAP5
component freezes? Will we be able to get 2.2.1 in?
Begin forwarded message:
> From: "Stefano Travelli (JIRA)" <jira-events(a)lists.jboss.org>
> Date: 18 March 2009 00:23:22 GMT
> To: pete.muir(a)jboss.org
> Subject: [JBoss JIRA] Commented: (JBSEAM-4011) Upgrade Drools
> framework integration to version 5
> [ https://jira.jboss.org/jira/browse/JBSEAM-4011?page=com.atlassian.jira.pl...
> #action_12457785 ]
> Stefano Travelli commented on JBSEAM-4011:
> As far as I know, drools 5 is not a drop in replacement of drools
> 4.0.7. Lots of dependencies change (mvel and antlr for instance) and
> most of all there are several API changes that make Seam after
> changeset #10170 not compatible with Drools 4 forcing a migration to
> Drools 5 in the run time environment of existing applications.
> At least, a detailed migration path for existing application is
> needed. However, even after accomplished all dependencies, rules in
> my application don't compile anymore.
> Actually, in my opinion this upgrade is unfitted for a maintenance
> release of Seam.
>> Upgrade Drools framework integration to version 5
>> Key: JBSEAM-4011
>> URL: https://jira.jboss.org/jira/browse/JBSEAM-4011
>> Project: Seam
>> Issue Type: Feature Request
>> Components: Drools
>> Reporter: Marek Novotny
>> Assignee: Marek Novotny
>> Fix For: 2.1.2.CR1
>> Upgrade Drools framework integration to current development version
>> of Drools 5. It is now available 5.0.0.CR1 version.
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly contact one of the
> administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
The message was undeliverable due to the following reason:
Your message could not be delivered because the destination computer was
unreachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.
Your message could not be delivered within 5 days:
Host 188.8.131.52 is not responding.
The following recipients did not receive this message:
Please reply to postmaster(a)lists.jboss.org
if you feel this message to be in error.