Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-4581

Update gradle build

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: Build
    • None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      The gradle build currently doesn't follow the recommended practises.

      The Logic shared between projects is highly mixed - resulting in different behaviour on upgrades to gradle. Eg: JAVA-4577 broke due to reliance on processing the javadoc.gradle and the custom aggregatedScalaDoc task.

      See: https://docs.gradle.org/current/userguide/organizing_gradle_projects.html

            Assignee:
            Unassigned Unassigned
            Reporter:
            ross@mongodb.com Ross Lawley
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: