-
Notifications
You must be signed in to change notification settings - Fork 137
[1328] Initial preparation for 5.0.0-M1 release #1331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: James R. Perkins <[email protected]>
…guration. Minor updates to the POM for the email addresses and remove the old SNAPSHOT repo. Signed-off-by: James R. Perkins <[email protected]>
c8be305 to
c36df1d
Compare
| </parent> | ||
|
|
||
| <distributionManagement> | ||
| <snapshotRepository> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do not support snapshots anymore? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do, it's in the parent-pom now, https://github.com/eclipse-ee4j/ee4j/blob/93c96342bad91438b61a94fbc48979f620a13625/parent/pom.xml#L298.
Signed-off-by: James R. Perkins <[email protected]>
Signed-off-by: James R. Perkins <[email protected]>
Signed-off-by: James R. Perkins <[email protected]>
c36df1d to
3298431
Compare
|
It's been 2 weeks and 3 approvals so I'm going to merge this. |
This is the initial preparation for an M1 release, see #1328.
The component upgrades are not required, but seemed useful.
I enabled all the previously disabled tests and tested against RESTEasy and WildFly. All tests passed with the exception of 1 test,
ee.jakarta.tck.ws.rs.api.rs.core.uribuilder.JAXRSClientIT.replaceQueryTest4. I've not looked into why, but we can look later..The one point on #1328 I need a second set of eyes on is "Version update to the new version number including updating Export and Import versions in API jar’s MANIFEST.MF and Specification document". I think that is updated correctly, but if not please let me know and I'll fix it.
This did yet tackle the "Updates for the SEO change in the specification document as outlined in". I need to look at that.