From: Lars H. <he...@se...> - 2009-08-13 14:51:48
|
Hi Markus, [...] > I'd simply concatenate the versions as follows: > "tinytim-meta-2.0.0a5-0.9.5.jar" (I prefer "meta" over "complete" here, > because there's also tinytim-console, tinytim-schema etc.) Thanks for the hint that these sub projects have to be maintained. ;) > This way, the engine version 'dominates' and it also shouldn't confuse > users, because it would still mean that a 'larger' combined version Okay, but the scheme would look like: tinytim-meta-2.0.0a5-2.0.0a5.jar which implies the tinytim version 2.0.0a5 and tinytim-mio 2.0.0a5. If tinytim-mio a6 is released, we get: tinytim-meta-2.0.0a5-2.0.0a6.jar > (the stituation where a newer engine version > requires an older mio version shouldn't be likely to happen, right?) Unlikely. :) Best regards, Lars -- Semagia <http://www.semagia.com> |