|
All,
I agree with Jim, so +1. Having said that, I don’t think the M1 for Jakarta REST is that useful for the purposed described below.
— Santiago
On Dec 6, 2023, at 10:59 AM, Jim Krueger via rest-dev <rest-dev@xxxxxxxxxxx> wrote:
One
of the intentions of the M1 release requested by the Platform Team was to provide a first
pass so that implementors could preview/consume and build using the API artifacts, potentially providing early feedback to shape the final version.
It is anticipated that there could potentially be backward compatibility issues. Avoiding any potential backward compatibility would require a fully functioning CI and completed TCK, which defeats the purpose I just mentioned. That is the goal for M2 not
M1.
For now my vote for providing an M1 version very soon and publishing on Maven Central is +1.
I understand and support the general idea, but I do not like the idea to have *milestones* (i. e. unfinished software) published in Maven Central in general, as the next
milestone can be backwards incompatible, which would not be compliant with SemVer. Milestones are not the aim of Maven Central, only final releases are (I know many projects do ignore that but they should not be taken as a role model). The typical Maven way
for such a situation is to use a separate pre-release repo. As we all use OSSRH (which IS a pre-release repo), we already need to refer to OSSRH already, so we can simply keep the milestones *there* unless JAX-RS 4 is *done* (and *then* push to Maven Central).
Anways, it is up to the JAX-RS committers to decide when and where to publish, so I invite all committers to discuss and vote. Note that each committer also has the possibility to veto, so we should find good arguments to convice each other and not just say
"others do that, so you must do that, too".
-Markus
Hi Markus,
Yes, it is true that it is ultimately your decision. However, the Platform Team's request is that Maven Central be used as this release's purpose is to make the API artifacts available for all implementers to consume. All the other specifications targeting
Jakarta EE 11 have complied with this.
(1) Nothing says that Maven Central MUST be used for publication. There are lots of other repos we could use to fulfil that email. (2) It might be the case that the Platform
team likes this to happen, but still this is the JAX-RS committer's decision if and what they put on Maven Central.
-Markus
Von: Ivar Grimstad [mailto:ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx]
Gesendet: Dienstag, 5. Dezember 2023 13:38
An: Markus Karg
Cc: Jakarta Rest project developer discussions
Betreff: Re: [rest-dev] M1 action items
Here is the request from the Jakarta EE Platform Project:
This message is your notice that the EE 11 platform project expects you, as a component spec project, to produce your first milestone release for EE11 by 23:59
EST on 2023-11-28.
Requirements
We want to keep the bar low for EE 11 M1. We realize we are all trying to get our milestone
release producing engines started. M1 does not require a TCK or an implementation, though it would be better if you had those. We will require those for M2. Here's what you need to hit M1.
-
API jar released to maven central
-
groupId: same as EE 10
-
artifactId: Same as EE 10
-
version: whatever your version number is for EE11 followed by "M1" For example for Jakarta Faces it would be 5.0.0-M1.
-
Spec document
-
Javadocs
-
XML schemas (if the spec has XML schemas)
When did the JAX-RS committers decide to do that?
-Markus
Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Ivar Grimstad via rest-dev
Gesendet: Dienstag, 5. Dezember 2023 11:09
An: Jakarta Rest project developer discussions
Cc: Ivar Grimstad
Betreff: Re: [rest-dev] M1 action items
Yes, the Milestones should be published to Maven Central.
Maybe I missed something, but why should we publish milestones publicly? IMHO we never did so befere.
If there is a concensus to publish milestones I will be happy to press that button for you.
-Markus
Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Jim Krueger via rest-dev
Gesendet: Dienstag, 5. Dezember 2023 03:13
An: rest Jakarta project developer discussions
Cc: Jim Krueger
Betreff: [rest-dev] M1 action items
Hi,
Please take a look at these to ensure they are correct. Assuming they are, if somebody on this list has authority and knowledge to run the Jenkins job to publish these to Maven Central please do so.
Beyond this, to finish M1 we will also need the following actions done:
-
Build the specification from the Release-4.0 branch
-
Add links to the M1 APIs in maven central and the M1 Specification to the project site
--
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse
Foundation Eclipse
Foundation - Community. Code. Collaboration.
--
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse
Foundation Eclipse
Foundation - Community. Code. Collaboration.
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
|
