on 5/13/02 4:19 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> what can we do to help with how Scarab does it's build? I would like to see Maven conform to Scarab's methodology for building itself. Scarab uses a sandbox methodology which allows the build process to function as a tool to generate everything into a "target" directory. This directory is special in that nothing in the original cvs checkout is modified in place...everything that is needed is copied into the target directory. The target directory is special because it is essentially a webapp directory. So, if you change a file in scarab/src/java/* and run ant, then it gets compiled into scarab/target/webapps/scarab/WEB-INF/classes so that the change is immediately seen. Scarab also does things like execute Torque on the fly to generate the code and SQL files into the right locations. Lastly, we also have targets in the build.xml to build Scarab's many number dependencies. Scarab's system does some tricky and complicated stuff, but it does it very cleanly and the build process is very easy to use. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
