Maven Shared Components
  1. Maven Shared Components
  2. MSHARED-47

maven-dependency-analyzer finds too many used dependencies

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Patch Submitted:
      Yes
    • Number of attachments :
      1

      Description

      I'll just quote the post from our internal mailing list:

      "I don't like that plugin - it has reported dozens of missing dependencies that were unnecessary for me, so I stopped using it. The most common example is when you have a dependency on a project that has a dependency on Xerces, Xalan or some other XML project and your project has java.xml.* imports, which you're resolving from the JDK, it gives a higher priority to external dependencies, even if another project introduces them, than it does to JDK libraries."

      I've got a (possible) patch coming up in a few...

        Issue Links

          Activity

          Hide
          Brian Fox added a comment -

          Cool. We should introduce a flag to the plugin to optionally ignore this, but looks good

          Show
          Brian Fox added a comment - Cool. We should introduce a flag to the plugin to optionally ignore this, but looks good
          Hide
          Herve Boutemy added a comment -

          I'm interested in this issue and have a few questions:

          • can you give me an example of such an artifact having a dependency on Xerces? I need to write a unit test
          • parsing the whole jdk does probably take a lot of time and memory: did you try to measure it?

          another idea would be to use JDK's api package list to detect classes to ignore: any objection?

          Show
          Herve Boutemy added a comment - I'm interested in this issue and have a few questions: can you give me an example of such an artifact having a dependency on Xerces? I need to write a unit test parsing the whole jdk does probably take a lot of time and memory: did you try to measure it? another idea would be to use JDK's api package list to detect classes to ignore: any objection?
          Hide
          Mirko Friedenhagen added a comment -

          Herve,

          I like your solution better, two questions come to my mind:

          • Is there an official list of the JDK's API packages? I see java, javax and maybe some org packages, is this really all?
          • For your solution do you suggest to put the JDK's api package lists into a shared JAR of it's own?

          I never encountered this, however the issue is quite old so maybe should just drop this.

          Show
          Mirko Friedenhagen added a comment - Herve, I like your solution better, two questions come to my mind: Is there an official list of the JDK's API packages? I see java , javax and maybe some org packages, is this really all? For your solution do you suggest to put the JDK's api package lists into a shared JAR of it's own? I never encountered this, however the issue is quite old so maybe should just drop this.

            People

            • Assignee:
              Brian Fox
              Reporter:
              Matthew Beermann
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: