Github user exabrial commented on the issue:
https://github.com/apache/tomee/pull/175
Fix TOMEE-2249
https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2249?filter=reportedbyme
by implementing required interfaces and executing method
---
GitHub user exabrial opened a pull request:
https://github.com/apache/tomee/pull/175
[tomee-7.0.x][TOMEE-2249] Fix EclipseLink NPE on init
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/exabrial/tomee
The primary way should imo ALWAYS to help the other projects we rely on to get
the releases out.
Falling back on a tomee internal release is only a last effort if the other
projects are not responsible.
LieGrue,
strub
> Am 28.09.2018 um 23:50 schrieb David Blevins :
>
>> On Sep 28, 2018, at
Agreed. If there's something that can be done to help them and the time to do
it fits in the target window, that should be the first attempt.
In a rare case a project may even accept help for the actual release.
WebServices project made me committer in 2006 so I could cut Axis 1.4 that was
I think we should do a big push to have TomEE 8 out before Oracle Code One.
With that said, we don’t have much time left, and since we still need to wait
for a vote on BVal and TomEE I was trying to cut some time from the TomEE
release if people would look at it now, and then when BVal is ready
