-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document user actions to manage dependencies for data flow apps #358
Comments
Hi, @dsyer. This is an old issue and unfortunately, we didn't talk about it for a long time - my apologies. From reading the description though, it is not clear whether if you're referring this in the context of the servers or the OOTB apps. For the latter, we have full-blown documentation on customizing existing and as well creating new apps. However, for the former, the most relevant bits would be the use of SCDF autoconfiguration module, which for example, is used in the PCF tile. If I'm misinterpreting, I'd be happy to clarify and/or add docs on that matter. Let me know. |
It was the latter I cared about. The docs you link to look good, but didn’t actually mention BOMs or dependency management at all. (Also noticed a spelling error in “appliation”.) |
Thanks, Dave. I should have pointed to the SCDF's stream-developer-guide, which is actually in the main ref. guide. Apart from selecting Boot + Binder from Initializer, there's nothing more to adjust the dependencies manually. Everything should be automatically set. We will revisit the content (including the typo) in app-starters docs via spring-attic/core#33. |
The use of the BOM and the interactions with other BOMs needs to be documented. For the short term the user should use spring-cloud-dataflow-dependencies and spring-cloud-dependencies in addition to spring-boot-dependencies (the latter might be included automatically in Gradle or in Maven when using the Boot parent pom). Later on, when data flow joins the Spring Cloud release train, only the cloud BOM will be needed.
The text was updated successfully, but these errors were encountered: