putting the version in the name of the jar file itself is actually the maven convention. i have approximately 75 deps on my eclipse classpath for the project i work on, and every single one of them is versioned in that manner. they are easily resolved and downloaded during build time because they adhere to that convention and have been published accordingly to some maven repo. why should h2 diverge from that convention?
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to h2-database@googlegroups.com To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
