JiriOndrusek commented on PR #8814: URL: https://github.com/apache/camel-quarkus/pull/8814#issuecomment-4855386764
> Actually, thinking more - perhaps option 2 is better. We maybe should not remove descriptions entirely? > > They show up in tooling and various places like central.sonatype.com & mvnrepository.com. I'm also not sure what happens at release time. I think there might be nexus rules around descriptions being mandatory (although if its missing it probably inherits from the parent or something...). In case the descriptions are necessary for other tasks/tools, we need to keep them. In that case, I will only do a clean-up of the descriptions. Possibly we can add some kind of validation `cq:check-descriptions`, which could compare the description with the catalog and be executed during mvn ` process-resources -Pformat` to fix a difference automatically. (which almost simulates the "automagic" with an empty description. (and add <cq.descriptionSync>false</cq.descriptionSync> into pom.xml, to avoid syncing in case of custom description) - default value = **true** -- 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]
