Latest viable JDK for Grails 5.1.4? - grails

I'm using Grails 5.1.4 for a number of projects now, and planning to move to 5.1.7 soon. I've been continuing to develop with Java 8 and deploy with Java 11, but I'm wondering whether there is a more recent version which I could be using without problems? The docs talk about the minimum JDK version required (8), but not the maximum usable one.

Related

Upgrading neo4j minor version

I have recently upgraded Neo4j from version 3.5 to version 4. The question is, in order to update Neo4j to the latest maintenance release, is it necessary to do all steps outlined in this link https://neo4j.com/docs/operations-manual/current/upgrade/, or it will be correct and sufficient to download the latest version and copy the data directory to the new Neo4j installation ?
The steps documented in the link has been done when moved from 3.5 to 4.0.3. I am going to update it from version 4.0.3 to version 4.0.4.
There is also a nice video from David Allen about the upgrade process
https://www.youtube.com/watch?v=GcaJ-aVLzr4

Log4j2 2.131. java supported version

What version of java supports latest version of Log4j2 2.13.1. Our application is using Java 8. From the official website I have got information for 2.12.1 mentioned as below but not for 2.13.1. Please let me know java 8 supports 2.13.1 version of Log4j2
Log4j 2.12.1 was the last 2.x release to support Java 7. Those artifacts can be found at:
This is the link: https://logging.apache.org/log4j/2.x/download.html
Log4j 2.3 was the last version to support Java 6 (and higher)
Log4j 2.12.1 was the last version to support Java 7 (and higher)
Log4j 2.13.0 and newer releases require a minimum of Java 8.
Log4j 3.0.0 is still in development and currently also requires a minimum of Java 8 but may end up requiring a minimum of Java 11.
This information is available on the Log4j 2 home page in the Requirements paragraph.

.net Core - compatibility of docker images

According to https://devblogs.microsoft.com/dotnet/announcing-net-core-3-0/, the newest version of .NET core should be backward compatible with the previous versions.
However, building a docker image with 2.2sdk won't run on a container with runtime 3.0... Am I missing something or is it the normal behavior?
There is no mention of that in the linked article?
What you are experiencing is normal behavior. Major versions are not backwards compatible (for runtimes).
In your case running a .net core 2.2 app will not work on an image with a .net core 3.0 runtime.
You can read more about version selection where the following is mentioned:
The host chooses the latest patch version installed on the machine. For example, if you specified netcoreapp2.0 in your project file, and 2.0.4 is the latest .NET runtime installed, the 2.0.4 runtime is used.
If no acceptable 2.0.* version is found, a new 2.* version is used. For example, if you specified netcoreapp2.0 and only 2.1.0 is installed, the application runs using the 2.1.0 runtime. This behavior is referred to as "minor version roll-forward." Lower versions also won't be considered. When no acceptable runtime is installed, the application won't run.
A few usage examples demonstrate the behavior, if you target 2.0:
2.0 is specified. 2.0.5 is the highest patch version installed. 2.0.5 is used.
2.0 is specified. No 2.0.* versions are installed. 1.1.1 is the highest runtime installed. An error message is displayed.
2.0 is specified. No 2.0.* versions are installed. 2.2.2 is the highest 2.x runtime version installed. 2.2.2 is used.
2.0 is specified. No 2.x versions are installed. 3.0.0 is installed. An error message is displayed.
They also mention roughly adhering to semantic versioning here:
MAJOR is incremented when:
Significant changes occur to the product, or a new product direction.
Breaking changes were taken. There's a high bar to accepting breaking changes.
An old version is no longer supported.
A newer MAJOR version of an existing dependency is adopted.

Does ASP.NET Core version have to match nuget package versions?

I'm trying to work out which version of the ASP.NET related packages I should be using.
We are trying to stick to LTS versions of ASP.NET Core, meaning we are still on version 2.1 and not 2.2 for the compiler and runtime. However I'm having a hard to trying to find out what version of the nuget packages we should be using.
for example, Microsoft.AspNetCore.Mvc says that its latest version is 2.2.0 and visual studio wants me to upgrade to this. However, I am wondering if we should stay on 2.1.3 since we are still on 2.1 for the compiler.
Are these version numbers related? Should we be staying back on 2.1.x to match pace with the compiler or are we doing things wrong?

Unable to add struts 2 support to netbeans 7.4

this plugin requires plugin Editor Library to be installed.
The plugin Editor Library is requested in version >= 2.10.1.10.2 (release version 2) but only 3.46.1.22.43 (of release version different from 2) was found.
The following plugin is affected:       Struts2 Support
Now i have resolved another plugin for Struts 2 support. This plugin is called Netbeans Struts2 Plug-in and its a re-pack for the plugin i was trying to install. Though this plugin in not certified but it is working good. The developers have tested it on netbeans 7.4 but i'm using it not netbeans8 and i have not suffered any issues.
I have found another way, that is using maven. That is also a good way but i would not recommend it if you have slow internet connection.

Resources