No central mechanism for the idea of release version? | Brian Pratt | 2009-10-09 10:22 | |||||||||||||||
Status: Closed | |||||||||||||||||
I bumped into an interesting problem in trunk where it appears we're building applets-9.3Beta.jar but the code still looks for applets-9.2.jar. That's an ugly sort of error. There is the version.properties file which appears to be where the 9.3Beta value was taken from, but it's not universally respected - upon inspection I find the string "9.2" liberally sprinkled through the codebase, including the string "applets-9.2.jar" in places like fileBrowser.js and drop.jsp. Rationalizing version info across a large project is tricky, of course, but I just thought I'd mention this since it took me a little while to figure out why my code changes didn't seem to be having any effect, and this might be an opportunity for improvement. Also it would appear that there's no automated test that catches this class of error? |
|||||||||||||||||
| |||||||||||||||||