The maintenance release 1.1.1. is being discussed.
Atm we don't have any SPI changes yet for 1.2.x, but that doesn't mean they
won't happen.
But, as the version change indicates, the changes should be back compatible.
e.g. possible mixin introduction
I know the first two issues are fixed, what's the status of the WELD-855?
Did you (Brian) and Pete get to the bottom of it?
I'll also check what else we can backport.
-Ales
On Mar 1, 2011, at 8:52 PM, Brian Leathem wrote:
Hello Weld devs,
I am under the understanding that the next Weld release will be Weld
1.2, with potential SPI changes. I am writing to ask about the
possibility of more frequent weld maintenance releases, using the same
SPI. This would greatly benefit the Seam 3.0 release, as there are a
couple of modules that currently do not work as expected due to bugs in
Weld. Specifically:
WELD-846 - Incorrect handling of cyclic dependencies between
BeanDeploymentArchives
causes: SEAMFACES-82, no injection in JSF Converters/Validators
WELD-833 - ConcurrentModificationException while deactivating conversations
renders Seam Wicket unusable
and potentially:
WELD-855 - Error while catching NonexistentConversationException with
Seam Faces/Catch
causes: SEAMCATCH-46
Some of these issues have been already resolved in Weld, and can be
worked around by using a Weld SNAPSHOT. However, it is probable that
more issues will arise as more people start using Seam 3, and a quick
turnaround on Weld releases would help greatly with user acceptance of
Seam 3. It would also bode well for containers that were quick to adopt
the Weld maintenance releases.
If there is any more details I can provide, or further strengthening of
the above arguments, please let me know.
Regards,
Brian Leathem
Seam Faces - Module Lead
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev