On Mon, 2002-03-18 at 01:49, Daniel Rall wrote:
> This directory structure is extremely confusing to someone not
> intimately familiar with Fulcrum development and Turbine's history.
> It doesn't even match up with the directory structures used by
> Turbine, Torque, Stratum, and Maven. I've had numerous complaints
> from other developers at CollabNet who've had to deal with the source
> tree. The tree should be normalized, either by dropping the "java"
I would be fine with this.
> directory off the end of each sub-directory of the "src" parent, or
> (preferably) by moving all application code under a single "java"
> directory.
-1
I want to be able to package up the core and the services separately. I
actually want to be able to completely separate the builds for the
services so that we can make them truly pluggable. I think this can now
be done with maven and it's something I will start on after the release
of 2.2 b1. I don't want to mix the core source with the service source.
It would be best, I think, to arrive at a common layout for service code
and allow people to make small build systems for a service so that all
the services that are out there can be contributed in a modular fashion.
> As I understand it, the Fulcrum source code was originally separated
> into these three directories ("core", "services", and "util") to
> differentiate between the various parts of Fulcrum, and to make
> building JARs containing individual services easier. A properly
> organized package structure does this job well, and coupled with Ant,
> individual service JARs can still be built just as easily.
I still don't think this is enough as I would like to easily be able to
incorporate all the service that people have written and adding every
service that people want to contribute to the repository would get out
of hand I think.
I want to make a maven build for the core and each of the services and
probably push the util code out to the commons.
Pete's docs for maven are coming along very well. And I have a tool that
is working to produce project descriptors pretty much automatically so I
believe it will be simple to split up the builds in addition to testing
them and trying them out with the core.
>
> [EMAIL PROTECTED] writes:
>
> > jvanzyl 02/03/17 12:09:46
> >
> > Modified: . project.xml
> > Log:
> > Fixing the sourceDirectory entries.
> >
> > Revision Changes Path
> > 1.6 +3 -3 jakarta-turbine-fulcrum/project.xml
> >
> > Index: project.xml
> > ===================================================================
> > RCS file: /home/cvs/jakarta-turbine-fulcrum/project.xml,v
> > retrieving revision 1.5
> > retrieving revision 1.6
> > diff -u -r1.5 -r1.6
> > --- project.xml 17 Mar 2002 01:00:02 -0000 1.5
> > +++ project.xml 17 Mar 2002 20:09:46 -0000 1.6
> > @@ -209,9 +209,9 @@
> > <build>
> >
> > <sourceDirectories>
> > - <sourceDirectory>src/core</sourceDirectory>
> > - <sourceDirectory>src/services</sourceDirectory>
> > - <sourceDirectory>src/util</sourceDirectory>
> > + <sourceDirectory>src/core/java</sourceDirectory>
> > + <sourceDirectory>src/services/java</sourceDirectory>
> > + <sourceDirectory>src/util/java</sourceDirectory>
> > </sourceDirectories>
> >
> > <testSourceDirectories>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
