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

Allow parsing a non-leaf module in a reactor build #971

Draft
wants to merge 10 commits into
base: version/revamp
Choose a base branch
from

Conversation

fabapp2
Copy link
Contributor

@fabapp2 fabapp2 commented Oct 17, 2023

Example:

Given a reactor build with four pom.xml: parent, A, B, and C where A depends on B and B depends on C.

reactor-build

When a dependency is added to B and the classpath changed

Then modules A and B must be parsed again to resolve the new types added.
While C is not required to be parsed again (it didn't change), the types provided by C must be made available when parsing B, and B's types must be made available when parsing C and so forth.

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

Successfully merging this pull request may close these issues.

1 participant