deploy: 2c8fd4f

Author: copybara-service[bot]

index.xml

@@ -63,7 +63,8 @@ Note that no Java protocol buffer methods accept or return nulls unless otherwis
 Compiler Invocation The protocol buffer compiler produces Java output when invoked with the --java_out= command-line flag.</description></item><item><title>Go Opaque API Migration</title><link>https://protobuf.dev/reference/go/opaque-migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/go/opaque-migration/</guid><description>The Opaque API is the latest version of the Protocol Buffers implementation for the Go programming language. The old version is now called Open Struct API. See the Go Protobuf: Releasing the Opaque API blog post for an introduction.
 The migration to the Opaque API happens incrementally, on a per-proto-message or per-.proto-file basis, by setting the api_level feature to one of its possible values:
 API_OPEN selects the Open Struct API. This was backported into edition 2023, so older versions of the Go plugin may not honor it.</description></item><item><title>Java Proto Names</title><link>https://protobuf.dev/reference/java/java-proto-names/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/java/java-proto-names/</guid><description>This document contains information on what the fully-qualified Java name of a proto is, based on the different proto options. This name corresponds to the package you need to import to use that message.
-Recommendation Set option java_multiple_files = true; Set option java_outer_classname = &amp;quot;FileNameProto&amp;quot;; Set option java_package = &amp;quot;com.google.package&amp;quot;; Explanation Multiple Files With java_multiple_files = true, the generated Java class for each message will be placed in a separate .</description></item><item><title>Java API</title><link>https://protobuf.dev/reference/java/api-docs-link/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/java/api-docs-link/</guid><description/></item><item><title>Go Opaque API: Manual Migration</title><link>https://protobuf.dev/reference/go/opaque-migration-manual/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/go/opaque-migration-manual/</guid><description>The Opaque API is the latest version of the Protocol Buffers implementation for the Go programming language. The old version is now called Open Struct API. See the Go Protobuf: Releasing the Opaque API blog post for an introduction.
+Recommendation Starting with Edition 2024, best practice is to:
+Set option java_package = &amp;quot;com.example.package&amp;quot; Do not set java_outer_classname or features.(pb.java).nest_in_file_class = YES. Starting with Edition 2024, the default behaviors have otherwise been improved so that now the default behavior is considered current best practice.</description></item><item><title>Java API</title><link>https://protobuf.dev/reference/java/api-docs-link/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/java/api-docs-link/</guid><description/></item><item><title>Go Opaque API: Manual Migration</title><link>https://protobuf.dev/reference/go/opaque-migration-manual/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/go/opaque-migration-manual/</guid><description>The Opaque API is the latest version of the Protocol Buffers implementation for the Go programming language. The old version is now called Open Struct API. See the Go Protobuf: Releasing the Opaque API blog post for an introduction.
 This is a user guide for migrating Go Protobuf usages from the older Open Struct API to the new Opaque API.
 Warning You are looking at the manual migration guide. Typically you’re better off using the open2opaque tool to automate the migration.</description></item><item><title>Go Opaque API FAQ</title><link>https://protobuf.dev/reference/go/opaque-faq/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/go/opaque-faq/</guid><description>The Opaque API is the latest version of the Protocol Buffers implementation for the Go programming language. The old version is now called Open Struct API. See the Go Protobuf: The new Opaque API blog post for an introduction.
 This FAQ answers common questions about the new API and the migration process.

reference/java/index.xml

@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Java Reference on Protocol Buffers Documentation</title><link>https://protobuf.dev/reference/java/</link><description>Recent content in Java Reference on Protocol Buffers Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://protobuf.dev/reference/java/index.xml" rel="self" type="application/rss+xml"/><item><title>Java Generated Code Guide</title><link>https://protobuf.dev/reference/java/java-generated/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/java/java-generated/</guid><description>Any differences between proto2, proto3, and Editions generated code are highlighted—note that these differences are in the generated code as described in this document, not the base message classes/interfaces, which are the same in all versions. You should read the proto2 language guide, proto3 language guide, and/or Editions language guide before reading this document.
 Note that no Java protocol buffer methods accept or return nulls unless otherwise specified.
 Compiler Invocation The protocol buffer compiler produces Java output when invoked with the --java_out= command-line flag.</description></item><item><title>Java Proto Names</title><link>https://protobuf.dev/reference/java/java-proto-names/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/java/java-proto-names/</guid><description>This document contains information on what the fully-qualified Java name of a proto is, based on the different proto options. This name corresponds to the package you need to import to use that message.
-Recommendation Set option java_multiple_files = true; Set option java_outer_classname = &amp;quot;FileNameProto&amp;quot;; Set option java_package = &amp;quot;com.google.package&amp;quot;; Explanation Multiple Files With java_multiple_files = true, the generated Java class for each message will be placed in a separate .</description></item><item><title>Java API</title><link>https://protobuf.dev/reference/java/api-docs-link/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/java/api-docs-link/</guid><description/></item></channel></rss>
+Recommendation Starting with Edition 2024, best practice is to:
+Set option java_package = &amp;quot;com.example.package&amp;quot; Do not set java_outer_classname or features.(pb.java).nest_in_file_class = YES. Starting with Edition 2024, the default behaviors have otherwise been improved so that now the default behavior is considered current best practice.</description></item><item><title>Java API</title><link>https://protobuf.dev/reference/java/api-docs-link/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/java/api-docs-link/</guid><description/></item></channel></rss>