Ticket #1076 (closed task: fixed)
Opened 2012-03-20T00:44:40-05:00
Last modified 2014-05-01T15:15:51-05:00
Add dependencyManagement section to scijava POM
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | minor | Milestone: | imagej-2.0.0 |
| Component: | Build System | Version: | |
| Severity: | non-issue | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1348 |
Description
Maven allows the uses of a dependencyManagement section to set the default version that will be used for a given dependency. This is cleaner than defining the preferred versions as properties like we do now. Update pom-scijava and its children to use inherited versions, where applicable.
Change History
comment:1 Changed 2012-04-24T13:10:56-05:00 by curtis
comment:2 Changed 2012-06-25T09:56:53-05:00 by curtis
- Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4
comment:4 Changed 2012-09-10T15:47:24-05:00 by curtis
- Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0
Not urgent. We should review and decide once and for all whether to do this by the final 2.0.0 release (there are reasons not to use a dependencyManagement section, too).
comment:5 Changed 2014-05-01T15:15:51-05:00 by curtis
- Status changed from new to closed
- Resolution set to fixed
While I was busy thinking about how urgent this task was not, dscho did the work and the result is totally awesome! Child POMs are much more readable now, and less error-prone.
At the same time, it would be good to start using the maven-enforcer-plugin to check for dependency convergence.