sebb> That's OK, except I don't see the need to move the runtime source sebb> files
As I said, standard layout makes codebase simpler to understand. What's your suggestion then? Note: current codebase contains resources and sources side by side. It makes build.xml hairy since it needs to exclude/include *.java and *.properties. When sources are located under src/main/java, and resources under src/main/resources, we don't really need to customize exclude-include in the build files. We won't get "accidental" variable replacement in the middle of the source code, and so on. sebb> particularly for a Proof of Concept. How do you tell a difference between a "Proof of Concept" and a workable build script? Current Gradle script: 1) Loads the project to IDE, so navigation works. 2) Downloads dependencies (it does not verify checksums yet, however it is trivial) 3) Builds jars, javadocs 4) Prepares lib/ folder, so ./bin/jmeter does launch JMeter I think it is quite close to cover all the features we need. Vladimir
