In order to attempt to straighten this out, I have written down some of the
results of the conversation in section 2.2 of the Cookbook. (Tomorrow
morning it will appear on the web site.) It is formulated as guidelines on
how to write the build.xml files.
I hope that you will all read through this and after some adjustments we can
adopt this as a policy.
What I think is the most controversial part is that I haven't
mentioned property files. I think most of the current mess is because we use
property files and especially include property files from other directories
pointing out things in a third place. While writing this I was thinking that
if we should use property files, their purpose is to list things that are
provided by some subsystem i.e. jar files, settings, or tools. Because of
that also the property file should be considered exported from the subsystem
and not, as it appears now, an attempt to collect information from all over
to reduce the amount of files. I would like to add this formulation too but
I would like to consider more options on how to use property files first.
/Linus
2008/5/6, Luis Sergio Oliveira <[EMAIL PROTECTED]>:
>
> Linus Tolke wrote:
>
> > Hello all!
> > On second thought, this was probably not such a good idea. I now think
> > that we should work to eventually remove the argo.root.dir directory.
> > The problem that you are addressing, Luis, is probably that to build
> > the other tigris projects, they have historically relied on having a whole
> > set of jars in ../argouml/build. This still works in the Repository layout
> > if the argouml/build.xml file is called that copies from
> > argouml/src/argouml-build/build to argouml/build. This does not, however
> > work in the Eclipse layout and since we try to allow the build.xml to work
> > also in the Eclipse layout this gets complicated. The only solution I can
> > think of is to have the argouml-build/build.xml create and copy all files to
> > ../argouml/build instead of build. That would allow the other tigris
> > projects to assume that everything is in ../argouml/build both in the
> > Eclipse layout and in the Repository layout. I don't like the solution very
> > much though. It is more appealing to have it within argouml-build.
> > Furthermore the argo.tools.dir must be handled in some way. It should
> > point to ../argouml/tools or ../argouml-core-tools depending on the
> > repository layout.
> > Note that I am trying to get rid of most of the properties specifying
> > directories and instead use relative paths. I think that will simplify
> > things a lot.
> > /Linus
> >
>
> OK, for the meantime I will commit something that will at least make the
> "install" target of the projects that depended on
> argouml-app/src/default.properties to work in SVN style checkout, so that
> the 0.25.5 isn't blocked by these.
>
> NOTE: I will only start committing at 23:30 GMT time, so, please shout if
> you want me to stop going forward.
>
> Regards,
>
> Luis
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
