Access to staged Jakarta EE 10 SPEC APIs...
by Scott Marlow
Hi,
I saw some discussion on the Jakarta Platform mailing list [1][2] asking
about this topic and wanted to make sure that all WildFly developers are
aware of how to access Jakarta EE 10 SPEC APIs that are staged but not
yet released to Maven Central (or whatever public repo).
The Jakarta EE staging repo [3] is specifically for Eclipse projects to
stage artifacts for development of an EE release. Once the SPEC API
artifact is officially released, it should be removed from [3]. The
contract is that staged artifacts can be deleted and or updated.
To get access to the staged artifacts, we can either update our
~/.m2/settings.xml [4] or add [3] to our project poms.
So that explains how we can access staged SPEC APIs. There are also
some implementation artifacts staged on [3] like EclipseLink, Yasson,
others.
Scott
[1] https://www.eclipse.org/lists/jakartaee-platform-dev/msg03135.html
[2] https://www.eclipse.org/lists/jakartaee-platform-dev/threads.html#03135
[3] https://jakarta.oss.sonatype.org/content/repositories/staging
[4] settings.xml:
<profile>
<id>jakartastaging</id>
<repositories>
<repository>
<id>jakarta-staging</id>
<name>Jakarta Staging</name>
<url>https://jakarta.oss.sonatype.org/content/repositories/staging/</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>jakartastaging</activeProfile>
.
.
.
</activeProfiles>
</settings>
4 years, 1 month
WildFly 26.0.1 Freeze is Friday 2022-01-14
by Jeff Mesnil
Hi,
The freeze date for WildFly 26.0.1.Final is Friday 14th January 2022.
Please file any PR against the 26.x branch and make sure that there is an
associated WFLY issue on our JIRA tracker.
In the JIRA tracker for the issue, make sure that it has 26.0.1.Final as
the Fix Version. In the PR please also link to any new or already merged
PRs against the main branch.
If the fix is needed for WildFly Core, use the 18.x branch and the WFCORE
issue tracker.
The freeze date for issues in WildFly Core is one day earlier (Thursday
13th January) as we need to release WildFly Core before the freeze date for
WildFly.
Note that the payload is meant to be limited, containing only critical
fixes, things community members are eager for etc., and component upgrades
addressing similar issues.
Any questions, please let me know.
Thanks,
Jeff
--
Jeff Mesnil
Principal Software Engineer
Red Hat
http://jmesnil.net/
4 years, 2 months
