We're updating the issue view to help you get more done. 

Move specification under Eclipse (EE4J umbrella)

Description

The transition has already been initiated, the specification page under the EE4J org is here (original proposal is here).

Next steps:

 

Specific actions for the spec repo:

  • check version of the tck-audit.xsl line 143: should we bump to 2.0.1?

  • check license of the tck-audit.xsl line 130 and consider changing it (me thinks no right now)?

  • Consider changing CONTRIBUTING.md to point to some eclipse email address instead? Update the website accordingly.

  • Update README.md to point to new repo for TCK tck-audit.xml file

 

Things needed clarification:

  • Concern about RI and which artifact to depend on (please clarify, )

  • The “How to Prepare…” document mentions an Eclipse license for JavaDoc; that’s not quite clear to me how this should work

  • TCK audit XML might need updating in case any assertions are affected by spec text changes

Other notes:

  • The API and spec master branches contain a very small number of commits done after the 2.0.1 release. AFAICS, they are only about typo and other minor fixes. So I think it’s fair to release them as part of the transitioned artifact

 

Environment

None

Status

Assignee

Emmanuel Bernard

Reporter

Gunnar Morling

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Priority

Major