eclipse-ee4j / eclipse-ee4j/glassfish-spec-version-maven-plugin

nonFinal, do we still need it?

Open
#23 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
2
Forks
6
PR merge metrics
No merged PRs in 30d

Description

The plug-in uses a convention for something called "nonFinal", which I think didn't carry over to Jakarta:

e.g.

```
// OSGi Bundle-SymbolicName: ${API_PACKAGE}-api
// OSGi bundle specversion: ${SPEC_VERSION}.99.b${SPEC_BUILD}
// OSGi Bundle-Version: ${SPEC_VERSION}.99.b${SPEC_BUILD}
// jar Extension-Name: ${API_PACKAGE}
// jar Specification-Version: ${SPEC_VERSION}.99.${SPEC_BUILD}
// jar Implementation-Version: ${NEW_SPEC_VERSION}-b${SPEC_BUILD}
```

Do we need to retain this?

@bshannon @romain-grecourt

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the glassfish-spec-version-maven-plugin code that generates the OSGi and JAR version metadata shown in the issue, and trace how the nonFinal convention is handled. Done means establishing whether Jakarta still requires these values and documenting a decided removal or retention path.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, release
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.