|
From: Colin B. <Col...@as...> - 2001-11-20 01:18:29
|
Go for it. -----Original Message----- From: Patrick Lacson [mailto:pa...@la...] Sent: Tuesday, 20 November 2001 11:52 To: BradLyon Cc: squirrel-dev Subject: Re: [Squirrel-sql-develop] Build re-org Guys, Would anybody object if I create a new module in CVS called "squirrel" that will apply the new BuildMagic system? Colin, your call.. -P BradLyon wrote: > > Great to have you involved, Patrick. I am not familiar with either > BuildMagic or JBOSS, but I am interested. > > At 10:41 AM 11/19/01 -0800, Patrick Lacson wrote: > >Colin, > > > >Hello everyone! Colin, thanks for getting me onboard and I look forward > >to contributing to this cool project! FYI, Colin and I have been > >discussing a build structure and possibly using the BuildMagic system > >that the JBOSS group uses, for simplification and ease of use. > > > >Colin, as it turns out from our last discussion, a lot of the work > >you've done in the CVS checkin of squirrel-sql can be easily ported to > >the buildmagic semantic. > > > >The BuildMagic tree structure adheres to the following semantic: > > > >modified files for project > >-------------------------- > >./build.xml (obvious) > >./project.xml (this is where all your project specific information is > >stored) > > > >buildmagic system files > >----------------------- > >./build.sh (script that uses the bundled ant lib instead of local ant) > >./etc/buildmagic/common.xml (system tree structure defaults) > >./etc/buildmagic/init.xml (system init defaults) > > > >source code info > >---------------- > >./src (source tree) > >./src/main (main src tree) > >./src/bin (executable scripts, batch files, etc) > >./src/etc (config files required for compilation or release) > > > >external tools and lib > >---------------------- > >./thirdparty (thirdparty applications/libraries like ice, izPack, > >jdbc-drivers, etc.) > >./tools (tools used for development testing such as junit, etc.) > > > >compile info > >------------ > >./output/build/classes (all files that are compiled from ./src/main > >./output/build/lib (contains the jar file when ./build jar is used) > > > >release info > >------------ > >./output/build/release/<version>-squirrel-sql/ (common doc and info) > >./output/build/release/<version>-squirrel-sql/bin (contains and > >executables) > >./output/build/release/<version>-squirrel-sql/classes (compiled > >byte-code) > >./output/build/release/<version>-squirrel-sql/api (java-doc files) > >./output/build/release/<version>-squirrel-sql/lib (bundled squirrel.jar) > > > >Basically this will keep things in a logical and intuitive structure. > >When we do a release a structure similar to 'release info' will be > >provided, granted that ./output/build/release/<version>-squirrel-sql is > >the root of tree. This is the structure that BuildMagic uses which we > >use here at work. Does anybody have any questions or comments? > > > > > > > >-- > ></Patrick> > >pa...@la... > > > >_______________________________________________ > >Squirrel-sql-develop mailing list > >Squ...@li... > >https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop _______________________________________________ Squirrel-sql-develop mailing list Squ...@li... https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop |
