Get ready for a 3.0 Release

[Shawn McKinney <sm...@apache.org>]

Beginning in a few weeks, I’ll be merging the changes for Jakarta compatibility.

The first release will bring partial Jakarta compatibility. Fortress Rest will support it and will require Tomcat 10 and beyond. 

The Web component will not. Why? Not all of its dependencies yet have support. It can’t migrate until every library it uses is compatible. So, it will (still) require Tomcat 9 and before.

If you’re just using the Core, of course you don’t care about Tomcat.

Regardless, every fortress component will require Java 11 and beyond.

There have already been notifications on this. I have not received any correspondence that this creates problems. So, no plans for maintaining a Java 8 compatibility stream currently.

The target release date for the 3.0 release (will it be a release candidate?) is July 1st, 2023. Don’t hold me to that date. It could be later, probably not sooner.

—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org

Re: Get ready for a 3.0 Release

[Shawn McKinney <sm...@apache.org>]

> On Jun 17, 2023, at 9:55 AM, Shawn McKinney <sm...@apache.org> wrote:
> 
> Update:
> 
> I did not point out earlier that Fortress Rest (enmasse) and web (commander) components will require >= Java 17, due to their reliance on Spring v6.
> 

Correction:

Only the Rest component requires Java 17. All of the others (core, realm, web) are Java 11.

> Again, this is part of the Javax to Jakarta migration. So, in order to “keep up” we are faced to adopt the latest versions of the JDK.
> 
> The others (core, realm) will require >= Java 11.
> 
> I’m hoping to get these changes merged soon. Have a bit more testing to do. If all goes well, will release in a week or so.
> 

Testing is complete. The Jakarta branches have been merged into master.  

Expect a 3.0.0 release within a week.


> —
> Shawn


---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org

Re: Get ready for a 3.0 Release

[Shawn McKinney <sm...@apache.org>]

Update:

I did not point out earlier that Fortress Rest (enmasse) and web (commander) components will require >= Java 17, due to their reliance on Spring v6.

Again, this is part of the Javax to Jakarta migration. So, in order to “keep up” we are faced to adopt the latest versions of the JDK.

The others (core, realm) will require >= Java 11.

I’m hoping to get these changes merged soon. Have a bit more testing to do. If all goes well, will release in a week or so.

—
Shawn

> On May 27, 2023, at 7:44 AM, Shawn McKinney <sm...@apache.org> wrote:
> 
> Beginning in a few weeks, I’ll be merging the changes for Jakarta compatibility.
> 
> The first release will bring partial Jakarta compatibility. Fortress Rest will support it and will require Tomcat 10 and beyond. 
> 
> The Web component will not. Why? Not all of its dependencies yet have support. It can’t migrate until every library it uses is compatible. So, it will (still) require Tomcat 9 and before.
> 
> If you’re just using the Core, of course you don’t care about Tomcat.
> 
> Regardless, every fortress component will require Java 11 and beyond.
> 
> There have already been notifications on this. I have not received any correspondence that this creates problems. So, no plans for maintaining a Java 8 compatibility stream currently.
> 
> The target release date for the 3.0 release (will it be a release candidate?) is July 1st, 2023. Don’t hold me to that date. It could be later, probably not sooner.
> 
> —
> Shawn


---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org