-
Feature Request
-
Resolution: Done
-
Minor
-
None
-
devstudio 10.1
-
None
-
devex docs #167 May 22-Jun 11, devex docs #168 Jun 12-Jul 3
-
5
Maven is "black magic" to the average developer and this task intends to capture the key scenarios that should be documented and/or tooling improved:
1) Why is THIS dependency needed? What specific component is using it?
2) Where did THIS dependency come from? What repository?
3) How can I work offline, off the net? How do I know an artifact that I am reaching for is not on my local machine? Not on my local network?
4) Since a property, determines the BOM and the BOM determines the versions of each included dependency, how can I trace those versions, see what is being used?
5) Often my local .m2/repository collects a "bad" artifact, how can I detect that and clean it up?
- relates to
-
JDF-51 Add Maven Setup & Troubleshooting Section
- Open