That would be really great if you could create Tickets and attach patches, txs
John
LieGrue,
strub
> Am 16.08.2017 um 01:25 schrieb John D. Ament :
>
> A 2.0.1 based on the current would be good, however I would recommend
> bringing in these two commits independent of the remaining work, since
A 2.0.1 based on the current would be good, however I would recommend
bringing in these two commits independent of the remaining work, since they
fix core issues.
- OWB isn't firing a before destroyed event -
https://github.com/johnament/openwebbeans/commit/10d62fca523f60a88616b8828cf4efccd845fadc
+1 for se in 2.0.2 and 2.0.1 sooner
If you nees help for SE on something specific, feel free to ping me.
Le 15 août 2017 14:37, "Mark Struberg" a écrit :
> Oki, that seems to be a bit more work to be left still.
>
> I'd then suggest to go on with the immanent features and release OWB-2.0.1
> pr
Oki, that seems to be a bit more work to be left still.
I'd then suggest to go on with the immanent features and release OWB-2.0.1
pretty soon while targetting 2.0.2 for the SE work.
txs and LieGrue,
strub
> Am 15.08.2017 um 13:48 schrieb John D. Ament :
>
> Mark,
>
> SE support is still a l
Mark,
SE support is still a long ways from being done. Most of the issues are
resolved, all of the remaining problems are related to OWB not honoring
when the container's been shutdown.
The good news, by removing the automatic starting of request context and
properly shutting down app context in
Hi folks!
I'd love to fix OWB-1209 and get Johns SE changes in.
I think we are then ready to roll a 2.0.1 release, isn't?
John, I'll be available on IRC to coordinate and review your proposed SE
changes.
Of course we could also discuss it via IRC, but might be easier to give that
feedback via
