Re: [jakartaee-platform-dev] Transitioning Jakarta EE to the jakarta nam

[Raymond Auge <raymond.auge@xxxxxxxxxxx>]

To point out the limitations of this graph, javax.annotation dependency is missing from at least CDI, JAXRS, JSF. True the dependency is not in API, it is part of these specs to which any change in the API which incurr a spec change and therefore also require such loosely coupled transition API/spec dependencies to change. I realize this is a much deeper review than can be done by just the API, but I feel omitting these is simply not representative of the real task.

A second phase should take the work above and add some meta information about such loose coupled dependencies.

- Ray

On Fri, Jun 21, 2019, 10:03 Guillermo González de Agüero, <z06.guillermo@xxxxxxxxx> wrote:

Wow thanks!

El jue., 20 jun. 2019 2:02, Lilian BENOIT <lilian.benoit@xxxxxxxxxx> escribió:

Hi,

I have generated dependency graph from your program with plantuml.
I think that it's more explicit than text only

I added also color to distinguish simple or complex case.
  - green  - simple case
  - yellow - complex case

The image is accessed at
https://raw.githubusercontent.com/lilian-benoit/jkta/master/src/main/resources/depends.png

I have realized PR pour add this functionality
https://github.com/tomitribe/jkta/pull/1

Currently, i generated text file. This file is passed as argument to
program plantuml.jar


Best regards,
Lilian.


Le 17/06/2019 07:08, David Blevins a écrit :
> 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