ammachado opened a new pull request, #24541:
URL: https://github.com/apache/camel/pull/24541

   # Description
   
   Fixes `OrderedProperties` containment support by delegating `containsKey`, 
`containsValue`, and legacy `contains` to the backing `LinkedHashMap`, and adds 
regression coverage for those semantics plus remove behavior.
   
   This also updates the Camel JBang export path in `ExportCamelMain` to use 
`containsKey(...)` for profile-based property presence checks, so explicitly 
configured keys are still treated as present even when their value is empty.
   
   Why: `BaseOrderedProperties` moved storage into a backing map but never 
overrode the inherited `Hashtable` containment methods, so property presence 
checks could return false even when the ordered properties instance actually 
contained the key.
   
   _AI-generated by Codex on behalf of ammachado._
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [x] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   
   - [ ] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   Verification note: I attempted focused Maven verification earlier, but it 
was blocked in the sandbox by the local Develocity `~/.m2` access requirements. 
The repo pre-push hook did run `mvn formatter:format impsort:sort` successfully 
during push.
   
   # AI-assisted contributions
   
   - [x] If this PR includes AI-generated code, commits have proper 
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR 
description identifies the AI tool used.
   


-- 
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