Re: [ee4j-pmc] Project/Specification dependencies

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

I submitted another pull request.

I think this is getting to be pretty close to accurate.

I removed the Jakarta EE platform because the picture was just too cluttered with it included and it didn't really add any value.

Is (or can) the svg output from "dot" published automatically on the web site to make it easy for people to review it?

Wayne Beaton wrote on 05/17/18 08:33 PM:

I've rolled in the pull request.

I tweaked the diagram a bit more. I decided to, for example, separate the projects not hosted as Eclipse Projects.

Wayne

On Thu, May 17, 2018 at 10:24 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

Wayne Beaton wrote on 05/17/2018 06:00 PM:

GlassFish absolutely needs the artifacts produced by the API projects; it won't function without them.

I understand. But I don't think that having the diagram indicate that GlassFish implements all of the specifications is useful. Like I said earlier, it's not clear to me that expressing the that Jakarta EE references all of the specifications, while true, is all that useful on the diagram.

GlassFish does implement JPA, but it implements JPA by way of consuming EclipseLink. This is the interesting relationship IMHO, as it describes the relationships between the projects and makes it clear that GlassFish doesn't implement that particular specification directly. 

Again, I'm pretty sure that GlassFish does implement EJB. IMHO, by saying GlassFish consumes EclipseLink, but implements EJB gives me more information about where to look for stuff.

I understand.  I just wanted to make sure we all agreed on what this picture is trying to capture.  I updated it with this in mind.  If you want to remove Jakarta EE, that's fine with me.

I'll take a look at the pull request.

Thanks.

--

Wayne Beaton

Director of Open Source Projects

The Eclipse Foundation