Timeline for Versioning Strategy for Service Interfaces JAR
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 6, 2014 at 22:28 | vote | accept | Colin M | ||
| Apr 29, 2014 at 22:54 | comment | added | BillThor | @ColinMorelli I believe the specification version may need to be maintained manually, as it may not be trivial to determine if the specification has changed. Implementation version would be incremented on build. If the interface packages are cleanly defined, it should be simple for the CI server to determine if any implementation classes have changed. Common jar build should only occur if there are changes to it's contents. | |
| Apr 29, 2014 at 14:14 | comment | added | Colin M | I agree with the general approach, but I'm trying to come up with a more concrete way of making that determination on the CI server. I'm trying to figure out how to determine if a new implementation version is being used. | |
| Apr 28, 2014 at 13:10 | history | answered | BillThor | CC BY-SA 3.0 |