orpiske commented on pull request #6462: URL: https://github.com/apache/camel/pull/6462#issuecomment-977594555
> > camel-dependencies -> camel-catalog -> camel-dependencies (sync-properties) > > No I dont think this is correct - its > > > camel-catalog -> camel-dependencies (sync-properties) > Actually, we do seem to build the [camel-dependencies before the catalog](https://github.com/apache/camel/blob/main/pom.xml#L72). > In the camel-catalog there is a maven plugin that sync that camel-dependencies. > > However what is the "problem" is that running camel-catalog should be done after all the components are build etc, which was tricky in the past with maven as it can build in "whatever order it thinks its best" - so there is this camel-allcomponents "trick". I understand. But it seems to me that we are using the catalog build only to refresh the dependency pom, no? BTW, I'm not trying to push to an specific solution here ... but it does seem odd that we have this cyclic dependency (but, as you know, I may be missing previous context here). -- 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
