JHipster 8.1, Piranha Cloud 23.12, Open Liberty 23.0.0.12, Tomcat Releases | Canada News Media
Connect with us

Tech

JHipster 8.1, Piranha Cloud 23.12, Open Liberty 23.0.0.12, Tomcat Releases

Published

 on

This week’s Java roundup for December 11th, 2023 features news highlighting: OpenJDK early access releases, Open Liberty 23.0.0.12, Infinispan 15.0.0-Dev06, JHipster 8.1.0, Piranha 23.12.0, Apache Tomcat 11.0.0-M15, 10.1.17, 9.0.84 and 8.5.97 and the debut of the Payara Virtual Conference.

JDK 23

Build 2 of the JDK 23 early-access builds was made available this past week featuring updates from Build 1 that include fixes for various issues. Further details on this release may be found in the release notes.

JDK 22

Build 28 of the JDK 22 early-access builds was also made available this past week featuring updates from Build 27 that include fixes to various issues. More details on this build may be found in the release notes.

For JDK 23 and JDK 22, developers are encouraged to report bugs via the Java Bug Database.

Spring Framework

Versions 6.1.2 and 6.0.15 of Spring Framework have been released to deliver bug fixes, improvements in documentation, dependency upgrades and new features such as: declare the isStatic() and releaseTarget() methods as default in the TargetSource interface; an improved @RegisterReflectionForBinding annotation for explicitly handling enums; and a resolution to avoid a race condition in the ConcurrentReferenceHashMap class. These versions may be consumed by the upcoming releases of Spring Boot 3.2.1 and 3.1.7, respectively. Further details on these releases may be found in the release notes for version 6.1.2 and version 6.0.15.

Versions 2023.1.1 and 2023.0.7 of Spring Data have been released providing bug fixes and respective dependency upgrades to sub-projects such as: Spring Data Commons 3.2.1 and 3.1.7; Spring Data MongoDB 4.2.1 and 4.1.7; Spring Data Elasticsearch 5.2.1 and 5.1.7; and Spring Data Neo4j 7.2.1 and 7.1.7. These versions may also be consumed by the upcoming releases of Spring Boot 3.2.1 and 3.1.7, respectively.

Open Liberty

IBM has released version 23.0.0.12 of Open Liberty featuring support for MicroProfile 6.1; updates to Liberty Maven plug-in 3.10, Liberty Gradle plug-in 3.8 and Liberty Tools 23.0.12 for Eclipse IDE, IntelliJ IDEA, and Visual Studio Code; and a resolution to CVE-2023-44487, a vulnerability in which Tomcat’s implementation of HTTP/2 was vulnerable to the rapid reset attack causing a denial of service that was typically manifested as an OutOfMemoryError.

Quarkus

The release of Quarkus 3.6.3 provides resolutions to: a regression in version 3.6.2 that yielded a NullPointerException from within the ConfigDiagnostic class; disabling of Dev Services for Keycloak leads to startup error; and a NullPointerException when Quarkus tries to match unknown configuration files. More details on this release may be found in the changelog.

Micronaut

The Micronaut Foundation has released version 4.2.2 of the Micronaut Framework featuring Micronaut Core 4.2.2 and updates to modules: Micronaut AWS and Micronaut Cache. Further details on this release may be found in the release notes.

Helidon

The release of Helidon 2.6.5 delivers: dependency upgrades, support for provider-specializing injection points in the OciExtension class; and correct errors in the documentation on how OpenAPI generator configuration settings are set. More details on this release may be found in the changelog.

Grails

The Grails Foundation has released version 6.1.1 of Grails Framework featuring big fixes, dependency upgrades and notable changes such as: resolve flaky tests by using different template names for each test; update Grails to, and make compatible with, Groovy 3.0.19; and a SnakeYAML BOM. Further details on this release may be found in the release notes.

Infinispan

The sixth development release of Infinispan 15.0.0 features notable changes such as: a reintroduction of support for JCache since its CDI aspects that depend on the javax namespace are optional making it possible to implement JCache without CDI; a resolution for the IllegalArgumentException thrown from the getMembersPhysicalAddresses() method defined in the JGroupsTransport class; and a check to ensure that the MetricsRegistry interface is enabled before trying to register metrics. More details on this release may be found in the changelog.

Micrometer

Versions 1.12.1 and 1.11.7 of Micrometer Metrics both deliver dependency upgrades and notable changes: a new ModifiedClassPathClassLoader class to synchronize with the version from Spring Boot; and a fix for duplication of publishing data if closing step registries before completion of the first step closes within one step. Further details on these releases may be found in the release notes for version 1.12.1 and version 1.11.7.

Similarly, versions 1.2.1 and 1.1.8 of Micrometer Tracing both provide dependency upgrades and a resolution to the default value of 0 returned by the getWallTime() method defined in the Event inner interface of the Observation interface causing backend failures when spans are uploaded. More details on these releases may be found in the release notes for version 1.2.1 and version 1.1.8.

Eclipse Vert.x

The release of Eclipse Vert.x 4.5.1 ships with notable changes such as: a switch from Locale.ROOT to Local.US for parsing PostgreSQL timestamps due to a change in JDK 22; a NullPointerException in the ForwardedParser class when the host header is missing for HTTP/1.1; and a new @JsonGen annotation that replaces the @DataObject annotation to trigger generation of a converter. Further details on this release may be found in the release notes and deprecations and breaking changes.

JHipster

The release of JHipster 8.1.0 features bug fixes, dependency upgrades and new features such as: use of a session endpoint metadata for OAuth logout; a refactor of the authorization header in the CustomClaimConverter class. More details on this release may be found in the release notes and this InfoQ news story on JHipster 8.0.

Project Reactor

Project Reactor 2023.0.1, the first maintenance release, provides dependency upgrades to reactor-core 3.6.1, reactor-netty 1.1.14 and reactor-pool 1.0.4. There was also a realignment to version 2023.0.1 with the reactor-kafka 1.3.22, reactor-addons 3.5.1 and reactor-kotlin-extensions 1.2.2 artifacts that remain unchanged. More details on this release may be found in the changelog.

Similarly, Project Reactor 2022.0.14, the fourteenth maintenance release, provides dependency upgrades to reactor-core 3.5.13, reactor-netty 1.1.14 and reactor-pool 1.0.4. There was also a realignment to version 2022.0.14 with the reactor-kafka 1.3.22, reactor-addons 3.5.1 and reactor-kotlin-extensions 1.2.2 artifacts that remain unchanged. Further details on this release may be found in the changelog.

Apache Software Foundation

Versions 11.0.0-M15, 10.1.17, 9.0.84 and 8.5.97 of Apache Tomcat all feature bug fixes and notable changes such as: background processes for a container no longer execute while lifecycle operations are in progress for that container; correct unintended escaping of XML in some responses from WebDAV; use an HTTP 408 status code, Request Timeout, instead of an HTTP 400 status code, Bad Request, if a read timeout occurs during HTTP request processing. More details on these releases may be found in the changelog for version 11.0.0-M15, version 10.1.17, version 9.0.84 and version 8.5.97.

The ninth alpha release of Apache Maven 4.0.0 delivers notable changes such as: a dependency upgrade to Maven Resolver 2.0.0-alpha-3; a multithreaded map/reduce algorithm to parse the lengthy reactor models in parallel; and the @SessionScoped annotation will now create proxies to wrap beans when there’s a need to inject a bean while the session scope is not yet available. Further details on this release may be found in the release notes.

Versions 3.21.3 and 3.20.9 of Apache Camel both feature dependency upgrades and notable bug fixes such as: an OutOfMemoryError upon initiating a large file upload via multipart; the addHeaderNameMethod() method defined in the EndpointDslMojo class generates the wrong header names; and configuration of Kubernetes secrets with Apache Camel K not working as expected. More details on these releases may be found in the release notes for version 3.21.3 and version 3.20.9.

Piranha

The release of Piranha 23.12.0 delivers notable changes such as: support for CRaC in the Payara Web Profile; an update to the Docker files to JDK 21; and a dependency upgrade to Spring Boot 3.1.6. Further details on this release may be found in their documentation and issue tracker.

OpenXava

The release of OpenXava 7.2.1 provides dependency upgrades and notable bug fixes such as: a Remote Code Execution vulnerability via XSTL from dependencies; use of an @OnChange action in @Coordinates not working as intended; and the idProperties attribute defined in the @Tree annotation was ignored. More details on this release may be found in the release notes.

Payara Virtual Conference

The first-ever Payara Virtual Conference, a one-day event, was held this past week featuring talks from top industry analysts, Java Champions and Jakarta EE experts. Attendees also learned more about the Payara Platform 2024 roadmap from Steve Millidge, CEO at Payara.

Source link

Continue Reading

Tech

Ottawa orders TikTok’s Canadian arm to be dissolved

Published

 on

 

The federal government is ordering the dissolution of TikTok’s Canadian business after a national security review of the Chinese company behind the social media platform, but stopped short of ordering people to stay off the app.

Industry Minister François-Philippe Champagne announced the government’s “wind up” demand Wednesday, saying it is meant to address “risks” related to ByteDance Ltd.’s establishment of TikTok Technology Canada Inc.

“The decision was based on the information and evidence collected over the course of the review and on the advice of Canada’s security and intelligence community and other government partners,” he said in a statement.

The announcement added that the government is not blocking Canadians’ access to the TikTok application or their ability to create content.

However, it urged people to “adopt good cybersecurity practices and assess the possible risks of using social media platforms and applications, including how their information is likely to be protected, managed, used and shared by foreign actors, as well as to be aware of which country’s laws apply.”

Champagne’s office did not immediately respond to a request for comment seeking details about what evidence led to the government’s dissolution demand, how long ByteDance has to comply and why the app is not being banned.

A TikTok spokesperson said in a statement that the shutdown of its Canadian offices will mean the loss of hundreds of well-paying local jobs.

“We will challenge this order in court,” the spokesperson said.

“The TikTok platform will remain available for creators to find an audience, explore new interests and for businesses to thrive.”

The federal Liberals ordered a national security review of TikTok in September 2023, but it was not public knowledge until The Canadian Press reported in March that it was investigating the company.

At the time, it said the review was based on the expansion of a business, which it said constituted the establishment of a new Canadian entity. It declined to provide any further details about what expansion it was reviewing.

A government database showed a notification of new business from TikTok in June 2023. It said Network Sense Ventures Ltd. in Toronto and Vancouver would engage in “marketing, advertising, and content/creator development activities in relation to the use of the TikTok app in Canada.”

Even before the review, ByteDance and TikTok were lightning rod for privacy and safety concerns because Chinese national security laws compel organizations in the country to assist with intelligence gathering.

Such concerns led the U.S. House of Representatives to pass a bill in March designed to ban TikTok unless its China-based owner sells its stake in the business.

Champagne’s office has maintained Canada’s review was not related to the U.S. bill, which has yet to pass.

Canada’s review was carried out through the Investment Canada Act, which allows the government to investigate any foreign investment with potential to might harm national security.

While cabinet can make investors sell parts of the business or shares, Champagne has said the act doesn’t allow him to disclose details of the review.

Wednesday’s dissolution order was made in accordance with the act.

The federal government banned TikTok from its mobile devices in February 2023 following the launch of an investigation into the company by federal and provincial privacy commissioners.

— With files from Anja Karadeglija in Ottawa

This report by The Canadian Press was first published Nov. 6, 2024.

The Canadian Press. All rights reserved.

Source link

Continue Reading

Health

Here is how to prepare your online accounts for when you die

Published

 on

 

LONDON (AP) — Most people have accumulated a pile of data — selfies, emails, videos and more — on their social media and digital accounts over their lifetimes. What happens to it when we die?

It’s wise to draft a will spelling out who inherits your physical assets after you’re gone, but don’t forget to take care of your digital estate too. Friends and family might treasure files and posts you’ve left behind, but they could get lost in digital purgatory after you pass away unless you take some simple steps.

Here’s how you can prepare your digital life for your survivors:

Apple

The iPhone maker lets you nominate a “ legacy contact ” who can access your Apple account’s data after you die. The company says it’s a secure way to give trusted people access to photos, files and messages. To set it up you’ll need an Apple device with a fairly recent operating system — iPhones and iPads need iOS or iPadOS 15.2 and MacBooks needs macOS Monterey 12.1.

For iPhones, go to settings, tap Sign-in & Security and then Legacy Contact. You can name one or more people, and they don’t need an Apple ID or device.

You’ll have to share an access key with your contact. It can be a digital version sent electronically, or you can print a copy or save it as a screenshot or PDF.

Take note that there are some types of files you won’t be able to pass on — including digital rights-protected music, movies and passwords stored in Apple’s password manager. Legacy contacts can only access a deceased user’s account for three years before Apple deletes the account.

Google

Google takes a different approach with its Inactive Account Manager, which allows you to share your data with someone if it notices that you’ve stopped using your account.

When setting it up, you need to decide how long Google should wait — from three to 18 months — before considering your account inactive. Once that time is up, Google can notify up to 10 people.

You can write a message informing them you’ve stopped using the account, and, optionally, include a link to download your data. You can choose what types of data they can access — including emails, photos, calendar entries and YouTube videos.

There’s also an option to automatically delete your account after three months of inactivity, so your contacts will have to download any data before that deadline.

Facebook and Instagram

Some social media platforms can preserve accounts for people who have died so that friends and family can honor their memories.

When users of Facebook or Instagram die, parent company Meta says it can memorialize the account if it gets a “valid request” from a friend or family member. Requests can be submitted through an online form.

The social media company strongly recommends Facebook users add a legacy contact to look after their memorial accounts. Legacy contacts can do things like respond to new friend requests and update pinned posts, but they can’t read private messages or remove or alter previous posts. You can only choose one person, who also has to have a Facebook account.

You can also ask Facebook or Instagram to delete a deceased user’s account if you’re a close family member or an executor. You’ll need to send in documents like a death certificate.

TikTok

The video-sharing platform says that if a user has died, people can submit a request to memorialize the account through the settings menu. Go to the Report a Problem section, then Account and profile, then Manage account, where you can report a deceased user.

Once an account has been memorialized, it will be labeled “Remembering.” No one will be able to log into the account, which prevents anyone from editing the profile or using the account to post new content or send messages.

X

It’s not possible to nominate a legacy contact on Elon Musk’s social media site. But family members or an authorized person can submit a request to deactivate a deceased user’s account.

Passwords

Besides the major online services, you’ll probably have dozens if not hundreds of other digital accounts that your survivors might need to access. You could just write all your login credentials down in a notebook and put it somewhere safe. But making a physical copy presents its own vulnerabilities. What if you lose track of it? What if someone finds it?

Instead, consider a password manager that has an emergency access feature. Password managers are digital vaults that you can use to store all your credentials. Some, like Keeper,Bitwarden and NordPass, allow users to nominate one or more trusted contacts who can access their keys in case of an emergency such as a death.

But there are a few catches: Those contacts also need to use the same password manager and you might have to pay for the service.

___

Is there a tech challenge you need help figuring out? Write to us at onetechtip@ap.org with your questions.

Source link

Continue Reading

Tech

Google’s partnership with AI startup Anthropic faces a UK competition investigation

Published

 on

 

LONDON (AP) — Britain’s competition watchdog said Thursday it’s opening a formal investigation into Google’s partnership with artificial intelligence startup Anthropic.

The Competition and Markets Authority said it has “sufficient information” to launch an initial probe after it sought input earlier this year on whether the deal would stifle competition.

The CMA has until Dec. 19 to decide whether to approve the deal or escalate its investigation.

“Google is committed to building the most open and innovative AI ecosystem in the world,” the company said. “Anthropic is free to use multiple cloud providers and does, and we don’t demand exclusive tech rights.”

San Francisco-based Anthropic was founded in 2021 by siblings Dario and Daniela Amodei, who previously worked at ChatGPT maker OpenAI. The company has focused on increasing the safety and reliability of AI models. Google reportedly agreed last year to make a multibillion-dollar investment in Anthropic, which has a popular chatbot named Claude.

Anthropic said it’s cooperating with the regulator and will provide “the complete picture about Google’s investment and our commercial collaboration.”

“We are an independent company and none of our strategic partnerships or investor relationships diminish the independence of our corporate governance or our freedom to partner with others,” it said in a statement.

The U.K. regulator has been scrutinizing a raft of AI deals as investment money floods into the industry to capitalize on the artificial intelligence boom. Last month it cleared Anthropic’s $4 billion deal with Amazon and it has also signed off on Microsoft’s deals with two other AI startups, Inflection and Mistral.

The Canadian Press. All rights reserved.

Source link

Continue Reading

Trending

Exit mobile version