db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Fischer <fisc...@seitenbau.net>
Subject Re: Subversion reorganisation?
Date Tue, 09 Aug 2005 10:17:00 GMT

Hi Henning,

Although I do admit I do not see all implications of it, the proposed
structure looks very good to me. If there are no other objections and
comments, I'd be glad if you could do the actual svn reorganisation,
because I have never worked with subversion before and would not like to
break anything. If you like, I could try and do the maven stuff next
weekend (clean up the maven.xml files, remove the project-base tricks, see
that the source and binary distributions work etc.)

I did not have time to look into the other runtimetest failure yet, and I
expect to have a busy week, so I'll look into this next weekend. Also when
you are done with the reorganisation, I'd like to reorganize the
runtimetest a bit (e.g. at the moment, if you change the generator
templates, one has to run maven jar in the templates directory for the
runtimetest to use the new templates, which is a nuisance; also I'd like to
convert the ant file fort the runtimetest into a maven thingy), and see if
the error persists after that.


"Henning P. Schmiedehausen" <hps@intermeta.de> schrieb am 08.08.2005

> >- would the runtime, generator, templates and the maven-plugin be
> >"independent" projects in the maven sense (i.e. would the
> >project-base.xml be removed and not be replaced) ?
> Yes they would. However, the files would not be removed.
> All files common to the three parts would be moved into the "common"
> module. In the sub projects, you add a subversion property to the tree
> which is svn:externals
> common   https://svn.apache.org/repos/asf/db/torque/common/
> this will pull the "common" directory automatically into the three sub
> projects. Inside of these, you will just refer
> "common/project-base.xml" as you did currently with "project-base.xml,
> ../../project-base.xml" and so on. The module will be the same for all
> three projects and still have its own tree in subversion.
> >- Instead of having different trunks for the runtime, generator etc it
> >would also be possible to have one trunk, and runtime, generator etc as
> >subdirectories. It seems to me that different trunks is better for
> >things decoupled, but one cannot have relative paths between the
> >parts of the projects any more. Or is this what the trunks directory is
> >for ?
> Yes. I got this idea from the jakarta/commons tree. Inside of
> "trunks", there will be svn:external references for all sub projects,
> so if you check out the trunks directory, you will get
> trunks/runtime          <--- same as runtime/trunk
> trunks/generator        <--- same as generator/trunk
> trunks/templates        <--- same as templates/trunk
> and inside of this "trunks" could also be e.g. a global maven.xml file
> which does a reactor build of all three projects.
>    Regards
>       Henning
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
> hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/
> RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for
>    Linux, Java, perl, Solaris -- Consulting, Training, Development
>             4 - 8 - 15 - 16 - 23 - 42
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message