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

Activity

Show:
Emmanuel Bernard
July 11, 2019, 2:21 PM
Edited

TODO:

  • Remove the references to JBoss repo in settings-example.xml

  • Evaluate dependencies we use and see if Eclipse cringes

  • Ask Eclispe which JDK 8 distro they use to test : it must have JavaFX

 

Guillaume Smet
July 11, 2019, 6:22 PM

Could we ask an official question about whether we could keep the history?

Gunnar Morling
July 11, 2019, 6:52 PM

Seems already asked Wayne about this (who is our mentor for BV at the EF), so let’s see what comes out of it.

Emmanuel Bernard
July 12, 2019, 7:57 AM

Follow the initial contribution process once we are happy with the packages:

https://www.eclipse.org/projects/handbook/#ip-initial-contribution

Guillaume Smet
July 12, 2019, 1:01 PM

We will also probably need to migrate the mailing lists (and all the references to them in TCK, API and documentation).

The relevant ones are: http://lists.jboss.org/pipermail/beanvalidation-dev/ and https://hibernate.atlassian.net/browse/BVTCK-210 .

Not sure if it should be done now (the one for the challenges is included in the TCK documentation)?

Assignee

Emmanuel Bernard

Reporter

Gunnar Morling

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Priority

Major
Configure