XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • devstudio 10.1
    • CodeReady Studio
    • 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?

            Unassigned Unassigned
            bsutter@redhat.com Burr Sutter
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: