Thread: Re: [Squirrel-sql-develop] Build re-org

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

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

Welcome aboard Patrick.

How would you see the plugins fitting into this? Being as they would need a
separate build process as well as being part of the main build.

Col

-----Original Message-----
From: Patrick Lacson [mailto:pa...@la...]
Sent: Tuesday, 20 November 2001 5:41
To: squirrel-dev
Subject: [Squirrel-sql-develop] Build re-org


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

After looking briefly at the plugins, they look like they would fit as
part of the main directory since they are actually compiled so it would
look something like:


./src
./src/main
./src/main/net/sourceforge/squirrel-sql/plugins/**
./src/main/net/sourceforge/squirrel-sql/client/**
./src/main/com/ice/util/**

./src/bin/*.bat and .sh scripts

./src/website/** contains all .html, .js, .css, .png, files related to
the website

./thirdparty/
./thirdparty/n3/lib/nanoxml.jar
./thirdparty/apache/lib/*xmlparsers and such
./thirdparty/whatever-else

when a distribution or 'release' in buld-magic terms, a directory called

./output/release/<version>-squirrel-sql/classes
./output/release/<version>-squirrel-sql/lib/squirrel-sql.jar
./output/release/<version>-squirrel-sql/doc/README and javadoc


So that's the jist of the new structure.  Anything compiled should be in
the ./src/main/** directory, while static libraries should remain in the
thirdparty/<vendor>/lib directory.

Colin,  I'll start on this and have the new workspace ready by either
wednesday night or thursday morning.

-P


Colin Bell wrote:
> 
> Welcome aboard Patrick.
> 
> How would you see the plugins fitting into this? Being as they would need a
> separate build process as well as being part of the main build.
> 
> Col
> 
> -----Original Message-----
> From: Patrick Lacson [mailto:pa...@la...]
> Sent: Tuesday, 20 November 2001 5:41
> To: squirrel-dev
> Subject: [Squirrel-sql-develop] Build re-org
> 
> 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

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