jakartaee / jakartaee/common-annotations-api

Request for Jakarta Annotation API 1.3.6 with Module Descriptor

Open
#140 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
67
Forks
42
PR merge metrics
No merged PRs in 30d

Description

Would it be possible to publish an version like `1.3.6` with a module descriptor?

When trying to link the module `com.sun.xml.ws@2.3.7`, the only module that fails is the `java.annotation`, which the latest version is the 1.3.5.

Currently in my build, I can create a module-info and I add it to the jar:
```sh
jdeps --generate-module-info tmp lib/jakarta.annotation-api.jar
javac --patch-module=java.annotation=lib/jakarta.annotation-api.jar tmp/java.annotation/module-info.java
jar uf lib/jakarta.annotation-api.jar -C tmp/java.annotation/ module-info.class
```

However, migrating this to a Maven build complicates a lot, and it would be very useful if there was old release with the module-info descriptor.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Maven build and release configuration for the jakarta.annotation-api artifact, then inspect the existing 1.3.5 JAR and its module naming with the jdeps commands shown in the issue. Done means a published 1.3.6 artifact includes a usable module descriptor and can be consumed from a Maven build without manual JAR modification.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.