From: Markus U. <mar...@gm...> - 2009-08-13 14:45:35
|
Hi all, > For (b) this could be more difficult. Maybe the engine version number > should rule and for each -mio release a patch level is added? > > tinytim-complete-{version}.sp1.jar > > Hmmm.... better ideas? :) > > The goal of the additional distributions should be to ease the start > with tinyTiM and not to confuse users... ;) > 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.) This way, the engine version 'dominates' and it also shouldn't confuse users, because it would still mean that a 'larger' combined version refers to a newer archive (the stituation where a newer engine version requires an older mio version shouldn't be likely to happen, right?) Ad astra, Markus |