Skip to content
This repository has been archived by the owner on Jan 21, 2019. It is now read-only.

ModuleDependencies #8

Open
vindiagram opened this issue Aug 19, 2015 · 1 comment
Open

ModuleDependencies #8

vindiagram opened this issue Aug 19, 2015 · 1 comment

Comments

@vindiagram
Copy link

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.

@mkleint
Copy link
Contributor

mkleint commented Aug 20, 2015

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants