| Re: [jakartaee-platform-dev] Updating 3rd partydependenciestojakarta |
It’s been a while since we saw that but if it works and transforms the Bytecode or similar, that would be a lot less pain and maintenance. Maybe someone could still talk the the authors of some of These libraries, but hopefully the more popular and active ones will eventually migrate anyway. Werner Sent from Mail for Windows 10 From: Kevin Sutter Steve,
I would recommend Talking to the Apache Folks here but Looking at e.g. https://issues.apache.org/jira/browse/FILEUPLOAD-291which requested using javax.portlet.ActionRequest (not subject to Jakarta btw either, I have no ideas, if the Portlet project plans to join Jakarta EE or the technology is too “legacy” for that?) it was not updated for nearly 2 years now, so the project does not seem too active, although a few tiny API changes were done about 2 weeks ago: https://github.com/apache/commons-fileupload/tree/master/src/main
So I would say talk to them, and if that’s not likely to happen at Apache soon enough and the Glassfish team can justify and maintain such a fork, then it could be worth considering.
P.s.: Does Glassfish 6 also plan to use the Java Module System, because if you really had to do such an internal fork, then it would be best to clearly mark that kind of module as consumable by Glassfish only.
Werner
From: Steve Millidge (Payara)
It’s used internally in GlassFish. We can do whatever is compliant with the ASL. However that is why I am asking.
Steve
From:jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Werner Keil
„We will be moving it to the new Namespace“ I don’t think you unless you are an Apache member or Commons File Upload committer are allowed to do that.
Not unless you fork it to a completely new Project that has Nothing to do with Apache and does not use org.apache.
Werner
From: Steve Millidge (Payara)
That is the question I am asking. We aren’t about to rip out Common File Upload so we will be moving it to the new namespace in order to ship GlassFish 6. Question is do we have a preferred way of doing this and what are the IP rules for Eclipse?
Steve
From:jakartaee-platform-dev-bounces@xxxxxxxxxxx<jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Werner Keil
As Long as Apache Commons does not upgrade to Jakarta EE 8 or 9, we have to use what’s there even if it is Based on an older Version of Java EE ;-)
Maybe the more Apache affine ones here like David could help or ask the Commons committers to deal with that, but I don’t see how that would correlate exactly with Jakarta EE 9 or Glassfish 6.
Werner
Sent from Mailfor Windows 10
From: Steve Millidge (Payara)
Jackson was used before JSON-P/JSON-B were a thing in GlassFish we could try to remove it but it could take a while.
Commons File Upload depends on javax.servlet and the GlassFish administration console uses it to upload deployments.
Steve
From:jakartaee-platform-dev-bounces@xxxxxxxxxxx<jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Werner Keil
Hi,
Jackson, that’s interesting, why is it used in parallel or instead of Jakarta JSON (Processing and Binding)?
I don’t see why Apache Commons File Upload should Change anything to Jakarta, or do you mean a new Version of it for use by GlassFish 6? I guess either someone at Eclipse like Wayne or Ivar should be able to help with the IP/CQ entries.
Werner
Sent from Mailfor Windows 10
From: Steve Millidge (Payara)
Hi All,
On the Eclipse Glassfish project we have found a number of external 3rdparty 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?
Thanks
Steve
_______________________________________________ |
