lburgazzoli commented on code in PR #13481: URL: https://github.com/apache/camel/pull/13481#discussion_r1528458617
########## catalog/camel-catalog/src/main/resources/org/apache/camel/catalog/capabilities.properties: ########## @@ -0,0 +1,17 @@ +## --------------------------------------------------------------------------- +## Licensed to the Apache Software Foundation (ASF) under one or more +## contributor license agreements. See the NOTICE file distributed with +## this work for additional information regarding copyright ownership. +## The ASF licenses this file to You under the Apache License, Version 2.0 +## (the "License"); you may not use this file except in compliance with +## the License. You may obtain a copy of the License at +## +## http://www.apache.org/licenses/LICENSE-2.0 +## +## Unless required by applicable law or agreed to in writing, software +## distributed under the License is distributed on an "AS IS" BASIS, +## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +## See the License for the specific language governing permissions and +## limitations under the License. +## --------------------------------------------------------------------------- +platform-http=other/platform-http-main Review Comment: yeah, it is a little bit different from how things are done since it is the catalog that "dictates" what is the artifact that provides such feature. Eventually we may find a way to annotate a component to the provider for a capability and then the catalog plugin can auto generate this file but if was a little bit too intrusive so I opted for this simpler way. Maybe there should be a camel main catalog and this file should be in the related catalog module. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
