There is no reason to use a proper build tool rather than build by h2 it own.For current h2 project, It's hard to get start contribute or build in IDE, I can not event import to intellij or eclipse after I add a proper pom.xml I can build it now. I tried to mavenize h2, It's quit easy, but the most hard part is
1. build installer 2. build doc 3. build several small jar Let's start from the last one, build several small jar, that's possible with assembly plugin, we need build android, jaqu, small, mvstore, client jar, this is what assembly plugin good at. But build a installer or doc is also doable buy running a shell from maven, see http://stackoverflow.com/questions/3491937,also we can keep the build tool in h2, just let maven do an exec. In development, build these three thing is needless,make the developer concentrate on the code, and the h2 is more friendly.It just like a normal java project. BTW, why not allowed the wiki on github, I think the wiki is the better place to hold the documents,and more developer can take part in to make document better.The document in h2, is kind of unmaintainable (for me). Just hope h2 be better ! -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
