What if a shared library employs external dependancies managed by gradle?

[Tommy Chang]

Hello,

I'm working on a Jenkinsfile which defines a pipeline with calling functions from a shared library with `@Library` notation. I'm facing a problem that: the library I used is written in groovy and managed by gradle, which employs some other dependencies on maven. When I triggered the build on this pipeline, it seems that those dependencies in `build.gradle` are not imported.

If is possible to add a Stage in the pipeline, so the Jenkins can solve all those dependencies required by the shared library? Or is there other methods I can employ where I do not need to copy all those dependencies from `build.gradle` and hardcode them at the beginning of my Jenkinsfile?