[Feature] Resolve Maven dependencies in depth

[shenyi0828]

Search before asking

• I had searched in the feature and found no similar feature requirement.

Description

dependency example:
a -> b1,b2
b1 -> c1,c2
b2 -> d1,d2,d3
when I set deps "a" in 'application dependency' . only a,b1,c1 is included, NoSuchMethod exception is raised for missing c1,c2,d1,d2,d3 .

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[shenyi0828]

code from MavenTool.scala

I thinkd streampark can only resolve 1st level deps, not recursively

[shenyi0828]

I have to set them all for first level deps, which is marked by red square

[wolfboys]

Thanks for your feedback. Indirect dependencies may lead to loading some unexpected dependencies, causing jar conflicts and job failures, making troubleshooting very troublesome. Therefore, only direct dependencies are loaded, so that users need to manually confirm the addition of any dependencies required by the job. If you have any good ideas, you are welcome to discuss them together.