Hurray. There are a few more questions and tasks for me to follow up on before this is all integrated.
0. (anyone see problems with where it is placed, style, etc? now's the time to pick it apart) 1. For this second, I committed my own build.xml file as taste-build.xml. Obviously that is not a long-term thing. I felt it worth pausing to ask what I should do here, just integrate with the normal build/test targets, and then adapt my other targets (such as the one that builds an EJB) and copy them in? I'll probably want to prefix the names with "taste-". 2. MySQL dependency. Funny, I realize that the only place my code actually depends on the MySQL driver is in the test code. Not surprising, since the main code properly accesses a DB via JDBC abstractions. So that means that until you download and add the mysql-connector-5.1.6 .jar file to lib/, it's just the tests that won't compile. :) And they won't all pass until you run a MySQL instance for it to test against. This is a bummer. I am sorely tempted to remove the JDBC-related unit tests entirely. It's crappy to remove good tests to appease a build system, but, here it's really tempting. Support for this idea? 3. EJB dependency. I know there was some question about the license status of the EJB/servlet .jar files. And while updating the pom.xml dependencies I noted that for some reason the main Maven repo does not have an EJB .jar. I know there was also some question about the utility of the EJB interface, period. Seems like a waste to throw it away, but, maybe should be placed in examples/ for whoever cares to dust off and compile? that would be cool by me and simplify things a little further. 4. Documentation. I will attempt to commit a revised version of my documentation page. Any pointers on what to include and not include and where to put it? It will be an adapted version of what is at taste.sourceforge.net
