1) for the original question about the scratch I purpose to move dev to trunk/archive/java/dev/scratch.
2) +1 for the Davids suggestion I purpose following modules axis/java/modules/core - engine and the basic stuff axis/java/modules/om axis/java/modules/deployment axis/java.mldules/wsdl dependencies are * om,wsdl, build on there own * engine depend on the om,wsdl * deployment depend on engine to writing the build with maven I think we can learn from geronimo build .. will find out how it works unless there are objections I am going to go ahead with this layout Thanks Srinath On Thu, 17 Feb 2005 08:25:53 -0500, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > +1 to enforce as per Alek's (and david's) suggestion. > > -- dims > > On Wed, 16 Feb 2005 23:23:43 -0500, Aleksander Slominski > <[EMAIL PROTECTED]> wrote: > > +1 to modules > > > > only be carefult odecode about right granularity of modules. one could > > say that AXIS1 is modular it has just one module with hundreds of files > > ... or you coul dcreate too many modules just like i did ... > > http://www.extreme.indiana.edu/viewcvs/~checkout~/xsul/java/modules/ > > > > i think that it is also good to have modular build system that enforces > > dependencies between modules by controling build order and what is javac > > classpath for each module built - this is realtively easy to do with ant > > (<path ..> is very powerful tool to build custom classpaths), example: > > http://www.extreme.indiana.edu/viewcvs/~checkout~/xsul/java/build.xml > > > > HTH, > > > > alek > > > > David Jencks wrote: > > > > > If I understand correctly the java version of axis 2 will be located > > > in svn at http://svn.apache.org/repos/asf/webservices/axis/trunk/java/? > > > > > > My impression is that axis is a fairly large project and has several > > > aspects or parts that may be used in different combinations. This > > > kind of structure is much easier to support if the parts are built > > > separately. > > > > > > Whether or not the initial commit is divided into sections I urge you > > > to set up the svn structure to support this kind of division. > > > > > > I would suggest starting with: > > > > > > modules/core > > > > > > and > > > > > > applications/samples > > > > > > Later you can separate code parts or add modules such as > > > modules/jaxrpc, modules/transport, modules/deployment, etc etc. If > > > you start with an expandable directory layout you wil, IMO, l save a > > > great deal of effort by not having to move stuff and refactory the > > > build system. > > > > > > many thanks, > > > david jencks > > > > > > On Feb 16, 2005, at 7:46 PM, Srinath Perera wrote: > > > > > >> Hi All; > > >> > > >> At the IRC chat team decide to move the prototype code to > > >> http://svn.apache.org/repos/asf/webservices/axis/trunk/java/ > > >> > > >> the package structure will be starting from above location > > >> src/ > > >> test/ > > >> samples > > >> maven.xml > > >> project.xml > > >> ... etc > > >> > > >> When I thought of doing it I got following issue; > > >> the dev directory is inside > > >> http://svn.apache.org/repos/asf/webservices/axis/trunk/java/ and then > > >> to ppl to checkout the axis2 the dev directory (which is too big and > > >> not needed for most of the users) wil be checked out. > > >> I think we should move the dev directory out, e.g. > > >> http://svn.apache.org/repos/asf/webservices/axis/trunk/dev/java > > >> > > >> thoughts > > >> thanks > > >> Srinath > > >> > > > > > > > -- > > The best way to predict the future is to invent it - Alan Kay > > > > > > -- > Davanum Srinivas - http://webservices.apache.org/~dims/ >
