eclipse-ee4j / jax-rpc-api Goto Github PK

Last CTS runs indicate no failures in this component. It's time to make a public release. Before the release make sure that Eclipse Release Review is passed and all dependencies have been released.

Tasks

• Update text files
• Generate "boilerplate" specification project
• Make a staging release
• Generate Stand-alone TCK test results
• Create a PR to jakartaee/specifications repository
• Update the Jakarta EE API jar by submitting a PR to the jakartaee-api project

See here for detailed instructions.

All current API libraries shipped must be distributed to Maven Central under a sub-package of the jakarta groupId. Before the first release Maven coordinates of this project must be changed as it's described here.

May I know what's the new release version and target date to support jakarta namespace change for servlet-api (javax.servlet)
Such as File:
https://github.com/eclipse-ee4j/jax-rpc-api/blob/master/api/src/main/java/javax/xml/rpc/server/ServletEndpointContext.java

This is a place holder issue for Pull request from javaee/javax.xml.rpc#4

Update Eclipse GlassFish to use the new version of your API (and implementation, if applicable) by submitting a PR to GlassFish.

Although a new version of GlassFish will not be released for Jakarta EE 8, we hope to release an update sometime later.

To test Jakarta EE 8 compatibility we need to create a Jenkins job on project's Cloud Jenkins instance formally testing the API against the relevant TCK and as needed, relevant CTS subset tests.

For projects that do not already have automated testing, there is provided parameterized Jenkins job that can be invoked to perform these tests. User provides a link to an Eclipse GlassFish test build and sets the test sub-set parameters:

• For CTS -- https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-certification/
• For Stand-alone TCKs -- https://ci.eclipse.org/jakartaee-tck/job/standalonetck-certification/

Additional instructions and guidance for using and directly running TCKs is available on this wiki. Also in the jakartaee-tck project repository.

• Integrate to Eclipse GlassFish
• Pass all CTS/TCK tests

#15 must be finished before starting working on this task.

A README file could come in handy to the newcomers :-)

This task is for creating a basic build CI/CD pipeline for this project on Eclipse infrastructure. More information is here: https://ci.eclipse.org/.

We need to create a release CI/CD pipeline for this project.

Use these documents as a reference:

• How to release the first Eclipse version of projects
• JSONP release job
• Release job on the new cloud infra

This is a place holder issue for Pull request from javaee/javax.xml.rpc#2

• Organization Name ("Organization") and, if applicable, URL
  Eclipse Foundation
• Product Name, Version and download URL (if applicable)
  Eclipse XML RPC 1.1.5
• Specification Name, Version and download URL
  Jakarta XML RPC 1.1
• TCK Version, digital SHA-256 fingerprint and download URL
  Jakarta XML RPC TCK 1.1.0, SHA-256: 305a15a216b358a4f1d92711ba7bc45f8b648cb5a74f33fdeb15da09611a0084
• Public URL of TCK Results Summary
  TCK results summary
• Any Additional Specification Certification Requirements
  None
• Java runtime used to run the implementation
  Oracle JDK 1.8.0_191
• Summary of the information for the certification environment, operating system, cloud, ...
  Linux
• By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.
• By checking this box I attest that all TCK requirements have been met, including any compatibility rules.

The very start of the doc is missing two substitutions that I see in the both the pdf and html versions:

All existing copyright notices, or if one does not exist, a notice (hypertext is preferred, but a textual representation is permitted) of the form: "Copyright (c) [$date-of-document] Eclipse Foundation, Inc. <>"

It looks like these are just bad placeholders that should be updated to use asciidoc attributes.

This is a place holder issue for Pull request from javaee/javax.xml.rpc#1

• Uptake new Eclipse versions of dependencies (if any). Use GlassFish 5.1 Release Tracker wiki to find components versions to use.

• Release to OSSRH staging repository

• Update GlassFish 5.1 Release Tracker with released version number.

This is a place holder issue for Pull request from javaee/javax.xml.rpc#3