Update libraries to newer versions (maven and 3rd party)
Issue #306
resolved
Original issue 306 created by @ysavourel on 2013-01-03T18:49:17.000Z:
Not a bug, just routine cleanup.
I have attached some reports, based on the logs from running
mvn versions:display-dependency-updates
mvn versions:display-plugin-updates
mvn dependency:analyze
mvn dependency:tree
Comments (2)
-
-
- changed status to resolved
- edited description
Closing it as "not a bug, but process" and "we kind of do it". We are more disciplined in doing this for each release.
- Log in to comment
We are better at this now, we update versions more often. And it is easier to do, with a central superpom.
We are still behind with a few libraries that changed APIs in incompatible ways (lucene).
But I would not consider this a bug, really, it is in the "continuous maintenance" class. Should we close it?