[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakarta.ee-community] About Profiles
|
That being the case, we would need to split packages into multiple JARs in order to be compatible with the Java module system, no?
Right. As I understand it, You can introduce new classes under an existing javax namespace but you cannot introduce new sub-packages under the javax namespace. I think that would allow enough flexibility to break up the Servlet spec into its own base and HTTP specifications without having to introduce a new namespace.
It's not really an EG any more, those times are gone ;-) but it will be interesting to see, how e.g. making Servlet modular works under its existing namespace javax.servlet as opposed to a need for change to something else (like "ee.jakarta.servlet", etc.)
I would hope that as long as certain packages or elements could be made optional it should still work under the existing namespace, while a completely new "HTTP API" some brought into the discussion, I am pretty sure this will no longer work under javax.something.
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
--
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community