Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Specification committee repos

I envision that the path for the information for a particular version of a specification will be:<code>/<version>

Where <code> is the short name of the specification (e.g. "activation").

I had assembled potential codes in the "Code" column on the Projects, Specifications, and Documents spreadsheet.


Input welcome.


On Tue, Jul 9, 2019 at 6:12 PM Scott Stark <starksm64@xxxxxxxxx> wrote:
For spec documents we need to replace the jcp website links with the corresponding links. Do you know what the format of the URL to a given spec project is going to look like? For example, Jakarta Enterprise Beans ( would have what corresponding root specification page,

On Jul 9, 2019, at 10:56 AM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:

There are now 3 repos for us to use to get our various parts done.


A "Hugo" site for inclusion in via github submodule.  This would be where we put the specifications as per Wayne's prototype at


Another "Hugo" site for inclusion in via github submodule.  This would be where we put the TCK Process 1.0, associated Guide and any other official Specification Committee documents.

Perhaps this could go in a location like so?


Wayne, do you have a preference?


This is where we would put various things like scripts to do the signing of final binaries and automation of various tasks we need to do on all specification projects, such as create PRs for boilerplate spec creation.

David Blevins

_______________________________________________ mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Back to the top