Hi there. I'm currently working around a defect in `1.5.2` that has been fixed since then. In this case it is scalaxbDispatchVersion pulling the wrong template for the async.The workaround is not obtrusive, but I wanted to see when the next release would be coming down the pipeline. If there is required support work for making that release happen sooner, I can try to help with that.
--
You received this message because you are subscribed to the Google Groups "scalaxb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scalaxb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi,Thanks for the reminder. I'll try to get the next one out in a few days.-eugene
On Tue, Apr 24, 2018 at 11:55 PM, Trent Schmidt <trent....@gmail.com> wrote:
Hi there. I'm currently working around a defect in `1.5.2` that has been fixed since then. In this case it is scalaxbDispatchVersion pulling the wrong template for the async.The workaround is not obtrusive, but I wanted to see when the next release would be coming down the pipeline. If there is required support work for making that release happen sooner, I can try to help with that.
--
You received this message because you are subscribed to the Google Groups "scalaxb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scalaxb+u...@googlegroups.com.
Hi there. I'm currently working around a defect in `1.5.2` that has been fixed since then. In this case it is scalaxbDispatchVersion pulling the wrong template for the async.The workaround is not obtrusive, but I wanted to see when the next release would be coming down the pipeline. If there is required support work for making that release happen sooner, I can try to help with that.