gnodet-bot commented on code in PR #26404:
URL: https://github.com/apache/camel/pull/26404#discussion_r4013012750


##########
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc:
##########
@@ -432,6 +432,16 @@ set here, because that would reject input that parses 
today. Routes that genuine
 an external DTD or parameter entity through this converter must supply their 
own
 `SAXParserFactory`.
 
+=== Component deprecation
+
+==== camel-minio
+
+The Minio GitHub repository has been archived on the 25th April 2026.
+The container images were removed from Docker Hub on September 2026.

Review Comment:
   Confirming @davsclaus's suggestion: the correct parameter name is 
`uriEndpointOverride` (not `uriEndpoint`), and the text has a typo 
(`exisiting`). Applying the suggestion as-is fixes both — the corrected URI 
example is accurate against the aws2-s3 catalog.



##########
components/camel-minio/pom.xml:
##########
@@ -29,8 +29,8 @@
     <artifactId>camel-minio</artifactId>
     <packaging>jar</packaging>
 
-    <name>Camel :: MinIO</name>
-    <description>Store and retrieve objects from Minio Storage 
Service</description>
+    <name>Camel :: MinIO (Deprecated)</name>

Review Comment:
   🔍 **Nit — convention:** The established pattern for deprecated components is 
to suffix only `<name>`, not `<description>`. All other deprecated Camel 
components leave `<description>` unchanged:
   
   - `camel-ognl`: `<description>Camel OGNL support</description>` (no suffix)
   - `camel-paho`: `<description>Camel Eclipse Paho support</description>` (no 
suffix)
   - `camel-opentelemetry`, `camel-tracing`, `camel-observation`: same
   
   Same applies to the matching `projectDescription` key in 
`component.properties`.
   
   ```suggestion
       <name>Camel :: MinIO (deprecated)</name>
       <description>Store and retrieve objects from Minio Storage 
Service</description>
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to