Test dependencies not included in project dependencies?
See original GitHub issueIs there a reason why requirements.txt
does not include -r tests/requirements.txt
?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Transitive libraries not included through project dependency
The easiest way to solve the problem is to use 'compile' instead of 'testCompile' for the dependency declarations in project 'common-test'. Also, the...
Read more >maven-dependency-plugin not showing test-scoped ...
The test dependencies of your dependencies are not part of your dependency tree. They are ignored by Maven. Share.
Read more >4.10. Adding Test-scoped Dependencies - Sonatype Help
If your project has war or ear packaging, a test -scoped dependency would not be included in the project's output archive. To add...
Read more >Maven – Optional Dependencies and Dependency Exclusions
When another project (Project-X) declares Project-A as a dependency in its POM, the optional nature of the dependency takes effect. Project-B is not...
Read more >Maven Dependency Scopes - Baeldung
This is the default scope when no other scope is provided. Dependencies with this scope are available on the classpath of the project...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@khorolets agreed – I was just curious to see if this was a deliberate decision 😃
@frol Your position makes a lot of sense—my question was mostly based on my inexperience. I think your documentation is already very good. I’m just starting out with flask (only did the basic tutorial and a few toy examples before) and I find my way around your code just fine. Thanks for this awesome resource!
@jkoelling Thank you for bringing this up to us. My thinking was just like the one @khorolets described. The root
requirements.txt
includes “just enough” dependencies to get things running. Also, there are no invoke commands related to testing, I treat tests as “opt-in” extension… I might need to re-evaluate my position, or just document things better.