Skip to content

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

Draft
fabapp2 wants to merge 10 commits intoversion/revampfrom
revamp/feature/879-parser-should-allow-parsing-of-javasources-when-dependencies-changed
Draft

Allow parsing a non-leaf module in a reactor build#971
fabapp2 wants to merge 10 commits intoversion/revampfrom
revamp/feature/879-parser-should-allow-parsing-of-javasources-when-dependencies-changed

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