Skip to main content
[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
Looking at the diagram the arrow points in the opposite direction to what I’d expect so I want to confirm my understanding. 

The arrow points from a package being renamed at a package that will be affected by the rename?

Alasdair

On Jun 18, 2019, at 1:56 AM, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:


Here is a better rendering of the graph (thanks Joakim).  
It would be interesting to evaluate any proposed incremental EE9 releases against this, as it does suggest that many partial renamings will be difficult to achieve.

regards



On Mon, 17 Jun 2019 at 09:40, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:

David, 
thanks for that info.
For those that would like to see that visually, I just did https://github.com/eclipse-ee4j/jakartaee-platform/pull/29 to graph the dependencies in webgraphviz.   It's not a great visualisation, so probably don't merge, but thought I'd make the PR to at least have the data available.

cheers


On Mon, 17 Jun 2019 at 07:09, David Blevins <dblevins@xxxxxxxxxxxxx> 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


--


--
<59602366-28939700-90cc-11e9-927a-373f41541b37.png>_______________________________________________
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

Back to the top