orpiske edited a comment on pull request #6462: URL: https://github.com/apache/camel/pull/6462#issuecomment-977583530
Can't we solve this by separating the concerns? I mean like separating refreshing the dependencies from the dependency management? We could use the [properties-maven plugin](http://www.mojohaus.org/properties-maven-plugin/) to write and read a properties file. One potential benefit is that, with this way we could remove the all duplicated dependencies which are also currently listed in the parent pom. IMHO it could make dependency maintenance much simpler and the build code smaller. Currently we have: `camel-dependencies` -> `camel-catalog` -> `camel-dependencies` (sync-properties) Instead, we could refresh the dependencies as part of the the `camel-parent` (or `camel-dependencies` ?) build. That way, it would become: `camel-parent` (or `camel-dependencies`) -> `camel-catalog` -> likely no need to regenerate anything related to the camel-dependencies itself. **Granted**: this is a much bigger proposition, I know, but may lead to a cleaner build and remove the cyclic dependency. -- 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
