Ticket #1654 (closed defect: wontfix)

Opened 6 years ago

Last modified 5 years ago

Fix MiniMaven when a dependency's version is specified as a non-SNAPSHOT revision range

Reported by: dscho Owned by: dscho
Priority: minor Milestone: imagej2-unscheduled
Component: Build System Version:
Severity: cosmetic Keywords:
Cc: Blocked By:
Blocking: #1714

Description

When building Fiji, the ImageJ version is stuck at the version MiniMaven first had a look for the newest version in said range. We should accept newer version as they become available, probably by downloading a new maven-metadata-version.xml at the same schedule as SNAPSHOT versions would be downloaded (once a day).

Change History

comment:1 Changed 6 years ago by bdezonia

  • Milestone set to imagej2-unscheduled

comment:2 Changed 6 years ago by bdezonia

  • Blocking 1714 added

comment:3 Changed 6 years ago by dscho

  • Priority changed from major to minor
  • Severity changed from serious to cosmetic
  • Summary changed from Fix MiniMaven when a dependency's version is specified as a non-SNAPTHOT revision range to Fix MiniMaven when a dependency's version is specified as a non-SNAPSHOT revision range

Now that pom-scijava does not use release version ranges any longer, the resolution is not utterly pressing anymore.

comment:4 Changed 5 years ago by curtis

  • Status changed from new to closed
  • Resolution set to wontfix

Since we do not use them anymore: let's worry about version ranges in MiniMaven only if a concrete need for them arises.

Note: See TracTickets for help on using tickets.