[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] Transitioning Jakarta EE to the jakarta namespace
|
If this is a resource issue of some kind, at this point I am pretty sure the community can step up to do relatively minor work like the actual package renaming, bug fixes and minor enhancements for most APIs. After all, this is how JAX-RS is moving forward these days. It is just a matter of commiting to finding people to do the work and recruiting people the right way. The Java EE Guardians certainly have done exactly this sort of work before and can do it again. It would of course help tremendously if there was some technical guidance and review from key vendors (in effect being nominal "leads").
Where the problem lies is doing big ticket, complex work like the binary compatibility piece for implementations like GlassFish. Could Oracle help with that or Payara? If so, I think we have a working formula to move forward or at least make a serious attempt at it.
Reza Rahman
Principal Program Manager
Java on Azure
Please note views expressed here are my own as an individual community member and do not represent the views of my employer.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Dominic Büchner <dbuechner93@xxxxxxxxx>
Date: 6/26/19 8:13 AM (GMT-05:00)
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Transitioning Jakarta EE to the jakarta namespace
IMHO it looks easier to run through a Big-Bang transition than picking every single depended API with the big risk to miss one or the other...
Isn't the next step to go through the graph and identify APIs that are likely to rename if we go incremental, we can then follow the dependencies to see which APIs would be left over - ie exactly how incremental can we be.
I'll go first... while it has not been formally agreed, there is an active group around javax.servlet and I fully expect there to be demand for at least some incremental change in the EE9 timeframe, so javax.servlet and all it's dependencies can be put in the very-likely-to-be-renamed-regardless category, which then affects:
- javax.faces
- javax.security.enterprise
- javax.security.jacc
- javax.servlet.jsp
- javax.faces
- javax.servlet.jsp.jstl
- javax.xml.rpc
Thanks for creating this. What are the next steps here? Did the graph
help us arrive at any decisions yet? If not, what else is needed to
arrive at a decision?
Reza Rahman
Principal Program Manager
Java on Azure
Please note that views here are my own as an individual community member
and do not represent the views of my employer.
On 6/17/2019 1:08 AM, David Blevins wrote:
> Ok folks, more data for us to look at.
>
> I've created a report of transitive dependents to answer the question, "if we rename api foo, what else has to be renamed?"
>
> - https://github.com/eclipse-ee4j/jakartaee-platform/blob/master/namespace/transitive.adoc
>
> Note we did have a report that showed maven dependencies. This is the logical inverse of a maven dependency graph. It's the incoming dependencies, transitively walked backwards.
>
> An example of why this is important.
>
> - fact: javax.ejb has a maven dependency on javax.transaction, javax.xml.rpc and javax.xml.rpc.soap
> - question: Does renaming javax.ejb cause javax.transaction, javax.xml.rpc and avax.xml.rpc.soap to be renamed?
> - answer: No. These apis do not have a reference to javax.ejb and therefore could stay in javax even if javax.ejb is renamed
>
> This graph was created by collecting all the jars published to Maven central in the jakarta groupId, parsing them with ASM to collect any form of "import", then chopping them up by logical api package.
>
> If you want to play with the code, you can find it here. I apologize in advance for the relative mess -- the code wasn't really created for sharing and therefore will be hard to follow.
>
> - https://github.com/tomitribe/jkta
>
>
> -David
>
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
--
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
