Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Updating 3rd party dependencies to jakarta

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.


On Mon, May 18, 2020 at 7:15 AM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:

Hi All,


On the Eclipse Glassfish project we have found a number of external 3rd party dependencies that need updating to the new namespace before we can release GlassFish 6. For example Apache Commons File Upload and Jackson and likely others as we get closer to release. Can anybody advise on how we should go about modifying and shipping these components both from a preferred technical approach and from an IP/CQ perspective?






jakartaee-platform-dev mailing list
To unsubscribe from this list, visit


Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020 - October 20-22

Back to the top