Hi, > not allows usage of network and compiled binaries. > We shall build everything from the source offline
I understand (and agree). > Ant build.xml but only move reference to a > class-path jars to a, e.g. "libraries.properties" H2 has the following compile time depedencies: servlet-api-2.4.jar lucene-core-3.0.2.jar (or optional 2.2.0) slf4j-api-1.6.0.jar org.osgi.core-1.2.0.jar I didn't find Lucene 3.0.2 and osgi.core at http://www.jpackage.org/browser. Should I rely on Lucene 2.2, or should the build work with *either* Lucene 2.2.0 or 3.0.2? What about osgi? Would it be a big problem if I used my own build tool, if it doesn't require any network connection ("./build.sh offline") if the right jar files are in the "ext" directory? I can add a file "libraries.properties" in the ext directory if it helps. Is there a better name for the "ext" directory (ext for "external dependencies")? If required, I can write a wrapper Ant build.xml that calls my build tool (but I prefer not to, actually). > 1. Source should contain ONLY sources. > 2. Should be compiled offline. > 3. Dependencies are managed by the package manager (RPM in our case). I understand. > So you now know what the hell is to be a Java packager for Linux. :-) Yes, it does sound ugly... > how to convert best Maven to Ant — would you like to share? Maven has some advantages, but: 1 - It pulls a *huge* amount of libraries from the network 2 - Building a project isn't always repeatable, I guess most current project can't be built in a few years. 3 - It doesn't verify dependencies (with *local* hash codes) 4 - You don't have a clear and simple list of dependencies 5 - You first have to install it (the right version of it) 6 - I don't like XML too much 7 - You can't debug the build 8 - It's hard to extend Ant is actually not much better, except for (possibly) points 1 - 6. That's why I wrote my own build tool. Which isn't popular so far, I know, but solves most of the problems. > Maybe you can help with some ideas how better to deal then? I think you need to do what you do now, explain the problem to project maintainers. Many aren't aware of the problems yet, including Apache projects. But I don't currently have the solution that would work for all projects I'm afraid. I will do the best I can for my projects. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
