I'm not familiar with Tapestry code but that sounds like a lot of if's and checking for version. If i'm not mistaken then it will pollute the code and maybe slow down applications (as every action will need to be checked) If it is possible then additional modules sounds as much better idea. If someone is upgrading library version then some minimal effort is required from his side (downloading new jar/changing maven). Some small additional effort (downloading second jar/adding maven dependency) should not be so exhausting, and will allow to avoid a lot of unnecessary code.
Regards Michał Gruca -- View this message in context: http://tapestry-users.832.n2.nabble.com/A-more-general-approach-to-configuring-for-compatibility-tp5846901p5859511.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
