You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2019. It is now read-only.
I have a project where I have a pom dependency with a scope of provided that within it has a list of dependencies. This allows my project to pull down and add these dependencies to the class path. But if i were to specify a module Dependency within the plugin configuration it will not modify the manifest and add the module dependency unless my project explicitly has the dependency specified in the project. It would be nice if the plugin would recognize inherited dependencies or allow me to explicitly specify the dependencies in the configuration without having them explicitly defined in my project.
The text was updated successfully, but these errors were encountered:
direct and transitive dependencies have different meaning within the context of nbm project. Your pom dependency should have the scope of 'import', not 'provided' and then it will likely work as expected.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a project where I have a pom dependency with a scope of provided that within it has a list of dependencies. This allows my project to pull down and add these dependencies to the class path. But if i were to specify a module Dependency within the plugin configuration it will not modify the manifest and add the module dependency unless my project explicitly has the dependency specified in the project. It would be nice if the plugin would recognize inherited dependencies or allow me to explicitly specify the dependencies in the configuration without having them explicitly defined in my project.
The text was updated successfully, but these errors were encountered: