eclipse-ee4j/management-api

Jakarta Management

management-api's Issues

Integrate to GlassFish

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

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

Public Release

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.

Update Eclipse GlassFish

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.

Compatibility certification request for Eclipse Glassfish 5.1 for Management API

• Organization Name ("Organization") and, if applicable, URL:
  
  Eclipse Foundation
• Product Name, Version and download URL (if applicable):
  
  Eclipse Glassfish 5.1
• Specification Name, Version and download URL:
  
  Jakarta Management 1.1
• TCK Version, digital SHA-256 fingerprint and download URL:
  
  Jakarta EE 8 TCK, SHA-256:
  847c80c9c80bea4682006f186292b68acdd0ce9b239d998856c3a379c3a7be50
• 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 Centos 7, Apache Derby
• 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.

Build CI/CD pipeline

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/.

Fix ArtifactIds in Maven Central

The ArtifactIds in Maven Central are not consistent.
The ArtifactId for the api is "jakarta.management.j2ee-api" but the ArtifactId for the parent is "management-api-parent". I suspect that "jakarta" should be added to the parent. Perhaps "j2ee" should also be removed from the api artifactid.

Jakarta EE 8 TCK for Management job

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.

Release to OSSRH staging repository

• 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.

Release CI/CD pipeline

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

Change Maven coordinates

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.

Names of published items are not consistent/correct on mirror site mvnrepository.com

See https://mvnrepository.com/artifact/jakarta.management.j2ee

• The API name "Jakarta Management J2EE API" should not have "J2EE".

• The parent name "Management API Parent" should be "Jakarta Management API Parent".

• "Jakarta Management Specification" should not be there at all.

Prepare Management API project for Jakarta EE 8 Release

Tasks

• Update text files
• Generate "boilerplate" specification project
• Make a staging release
• Generate Stand-alone TCK test results - Not required. Covered by Platform TCK.
• Create two PRs to jakartaee/specifications repository (spec and apidocs).
  Spec Draft PR: jakartaee/specifications#75
  Apidocs (Javadoc) Draft PR: jakartaee/specifications#74
• Update the Jakarta EE API jar by submitting a PR to the jakartaee-api project. PR #25

See here for detailed instructions.

Add README file

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

Prevent spec from publishing in Maven Central

For version 1.1.4 the management-spec was published to Maven Central. While this likely cannot be removed, we should not publish future releases so it is important to determine why this happened and prevent it in the future.

https://search.maven.org/classic/#search%7Cga%7C1%7Cg%3A%22jakarta.management.j2ee%22

Place holder issue for Pull Request 1

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

Task for updating POM.xml with groupId fix for 'jakarta'

Make the changes needed corresponding to javaee/spec-version-maven-plugin#5