In another thread, and partly documented in the Cookbook section 2.2, we are
discussing the use of the properties and how to set them up. After the
recent move, this is not fixed everywhere and I guess it has never worked
for the argouml-java project.
The plan is, however, just to support two different checkout schemes, the
repository layout and the Eclipse layout.
In the repository layout you check out using more or less:
for proj in argouml argouml-java argouml-whatever
do
svn co http://$proj.tigris.org/svn/$proj/trunk $proj
done
and build using more or less
ANT=`pwd`/argouml/tools/apache-ant-*/bin/ant
for proj in argouml argouml-java argouml-whatever
do
( cd $proj && $ANT install )
done
In the Eclipse layout you check out from within Eclipse using the prepared
psf files (Project Set Files) and everything builds automatically. This
requires Subclipse!
That much is more or less working already although it might not be in place
for all subprojects. What we are having problems with is that we want to run
ant to build when everything is checked out in the Eclipse layout and the
magic involved to point out different directories relative to each-other is
a mess.
We are not considering preparing for other layouts like the one you are
discussing here. There is still some work to do to empty and remove
the modules directory completely but I hope we will get around to that
eventually. The dev module will then be a subsystem (in src/argouml-core-dev
or src/argouml-debug-dev or something similar) that is provided when working
from the source but not built into releases.
/Linus
2008/5/20, "Andreas Rückert" <[EMAIL PROTECTED]>:
>
> Hi!
>
> -------- Original-Nachricht --------
> > Datum: Tue, 20 May 2008 16:57:14 +0200
> > Von: "Thomas N." <[EMAIL PROTECTED]>
> > An: [email protected]
> > Betreff: Re: [argouml-dev] Problem with building the modules
>
> > Hi Andreas,
> >
> > you should just modify
> >
> > <property name="argo.root.dir" value="${basedir}/.."/>
>
> Does not work here. The argouml-java module is in
> argouml/modules/argouml-java
> , so the argo.root.dir is
> <property name="argo.root.dir" value="${basedir}/../.."/>
> the following line also seems to be wrong:
> <property name="argo.app.dir" value="${argo.root.dir}/argouml-app"/>
> , because after the SVN checkout it's actually
> <property name="argo.app.dir" value="${argo.root.dir}/src/argouml-app"/>
>
> Finding the build directory should become:
> ==========
> <!-- figure out where main ArgoUML build directory is -->
> <!-- TODO: This probably needs to reference the packaging directory -->
> <available file="${argo.root.dir}/../argouml-build/build"
> type="dir" property="argo.build.dir"
> value="${argo.root.dir}/../argouml-build/build"/>
> <available file="${argo.root.dir}/../argouml/src/argouml-build/build"
> type="dir" property="argo.build.dir"
> value="${argo.root.dir}/../argouml/src/argouml-build/build"/>
> ==========
> (The first check should never succeed, as I see it, so it might be
> removed?)
>
> I get a lot of warnings, but the module compiles then...
>
> > You are right, other references to argouml files should not depend on
> > ${basedir} any more!
> >
> > Either fix it, or let the checkouts of the projects argouml and
> > argouml-java live on the same directory level, i.e.
>
> May I send you my current version, so you can check it, before it gets
> committed to SVN?
>
> > /some_folder/argouml/ (src/argouml-build/ etc.), and
> > /some_folder/argouml-java/
>
> Not good. We have a modules directory in the argouml directory. Why not use
> it?
>
> Ciao,
> Andreas
>
> --
> 249 Spiele für nur 1 Preis. Die GMX Spieleflatrate schon ab 9,90 Euro.
> Neu: Asterix bei den Olympischen Spielen: http://flat.games.gmx.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
