Droids
  1. Droids
  2. DROIDS-134

Use explicit versions for the Maven dependencies

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.2.0
    • Fix Version/s: 0.2.0
    • Component/s: None
    • Labels:
      None

      Description

      It's best practice to define the Maven dependencies by using explicit versions. This improves the repeatability of the build, as it doesn't depend on the releases of new versions of these dependencies to Maven central.

      1. maven3.patch
        3 kB
        Tobias Rübner

        Activity

        Hide
        Tobias Rübner added a comment -

        This patch removes the plugin version warnings generated by maven 3.

        Show
        Tobias Rübner added a comment - This patch removes the plugin version warnings generated by maven 3.
        Hide
        Tobias Rübner added a comment -

        now with ASF licence

        Show
        Tobias Rübner added a comment - now with ASF licence
        Hide
        Richard Frovarp added a comment -

        Looks like this has been fixed. mvn versions:display-dependency-updates doesn't report back any unversioned dependencies.

        Show
        Richard Frovarp added a comment - Looks like this has been fixed. mvn versions:display-dependency-updates doesn't report back any unversioned dependencies.

          People

          • Assignee:
            Unassigned
            Reporter:
            Eugen Paraschiv
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development