Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Fwd: Move platform API jar file and javadoc generation to platform project?
+1

On Fri, 26 Apr 2019, 21:29 Wayne Beaton, <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
PMC... 

When significant functionality is moved from one project to another, the EDP requires that we engage in a Restructuring Review. The purpose of the Restructuring Review is to first ensure that the scope of the projects does not change, and to provide a means for the community to respond to the event (it's also the case that certain reviews trigger IP Policy obligations, but AFAICT that doesn't apply here). 

Ultimately, the EMO depends on the PMC to validate whether or not a change is significant.

Assuming that I understand correctly, this operation will just move a couple of build scripts. I don't believe that this represents the movement of significant functionality (with no obvious impact on any scope) and so I recommend that we just +1 this with a gentle reminder to the project team to ensure that their community is aware that the change is being made.

HTH,

Wayne

On Fri, Apr 26, 2019 at 1:52 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
I guess I should've sent this here as well...

PMC, any objections to moving this functionality?


-------- Forwarded Message --------
Subject: Move platform API jar file and javadoc generation to platform project?
Date: Thu, 11 Apr 2019 11:29:14 -0700
From: Bill Shannon <bill.shannon@xxxxxxxxxx>
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>,
jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>

(Sorry for the cross-posting, but presumably both groups will be interested...)

The Jakarta EE platform javadocs and API jar files are generated from a
subproject of the GlassFish repo.  A normal build of GlassFish does not build
this subproject, and a normal release of GlassFish does not release this
subproject.  This subproject collects together all the API artifacts from
all the other API projects, builds them, combines them into the platform
(and profile) API jar files, and generates the combined platform (and profile)
javadocs.

The reason this is part of the GlassFish repo is so that it can share
the configuration of the *versions* of the API artifacts; the actual API
artifacts used by the subproject are defined in the subproject.

I propose moving this subproject to a new repo in the Jakarta EE Platform
project.  This new Maven project can produce a BOM pom that can be imported
into GlassFish so that the artifact version configuration can still be shared.

Updating GlassFish to use a new version of a component may require updating
the API version in the Jakarta EE platform project and updating the
implementation version in the GlassFish project.  This will be a minor issue
for components with a clean API/implementation separation, but will be more
of an issue for components that require synchronized updates of both artifacts.

Questions?  Comments?  Concerns?

If there are no objections by April 18, I'll start the process to move
this Maven subproject to a jakartaee-api repo in the Jakarta EE Platform
project.

Thanks.
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc


--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc

Back to the top