Skip to content
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

Cascade project configuration changes to child projects #638

Closed
shawmanz32na opened this issue Sep 13, 2018 · 0 comments
Closed

Cascade project configuration changes to child projects #638

shawmanz32na opened this issue Sep 13, 2018 · 0 comments

Comments

@shawmanz32na
Copy link

Given a Maven project with a parent POM and two child modules and VS Code configured with "java.configuration.updateBuildConfiguration": "automatic", it'd be awesome if changes to the parent POM would cause the parent project AND the child modules' projects to be updated. Currently, changes to the parent POM cause only the parent project to be updated, and users must run the Java: Update java configuration command on each of the child projects before the project changes are applied.

This relates to #621, but differs in that this speaks about automatically applying the changes to child projects, while #621 speaks more to specifying which project(s) are to be updated when the Java: Update java configuration command is run from outside the context of a build file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants