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
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
Mail for Windows 10
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
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
Mail for Windows 10
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?
Thanks
Steve
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev