| Re: [jakartaee-platform-dev] Updating 3rd party dependencies to jakarta |
|
Thanks Wayne. Essentially these would hopefully be temporary forks needed to get a release of GlassFish and therefore Jakarta EE 9 out of the door without being dependent on persuading upstream projects out of
our control to adopt and make a new release in the Jakarta EE 9 namespace. I will pick up with you on the each individual dependency and our approach to managing it. Steve From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Wayne Beaton Ideally, the owners of these code bases will make and maintain the updates. Or at very least accept your contributions. From the perspective of the Eclipse IP Policy, the resulting libraries would then be new versions of existing third
party dependencies and subject to IP review/vetting. If you do end up needing to create a fork of anything at the Eclipse Foundation, the nature of the dependency changes from being third party to (effectively) being project code and so further due diligence may be required. Check in with
the IP Team before you start forking repositories. My recommendation is to first get a sense of what you need to do technically, and I'll help you sort out the best way forward with respect to the IP Policy. Wayne On Mon, May 18, 2020 at 7:15 AM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:
-- Wayne Beaton Director of Open Source Projects |
Eclipse Foundation, Inc. Join us at our virtual event:
EclipseCon 2020
- October 20-22 |