On Wed, Apr 30, 2008 at 10:36 AM, Linus Tolke <[EMAIL PROTECTED]> wrote:

> Another thing to consider is perhaps the role of the
> /trunk/src/argouml-build/build.xml. The reason for moving it lower is to
> allow it to be checked out on the same level as the Eclipse
> projects/subsystems. This is to be able to run the targets that builds every
> subsystem and runs the tests in every subsystem.
>
> The target that copies everything from each subsystem to whatever export
> directory is not applicable. Perhaps we should split that file and move the
> copying to /trunk/build.xml to make the argouml project work just like the
> other projects for the non-Eclipse checkout. The build.xml will then contain
> more or less:
>      build each subsystem
>      copy the result of the builds to build.
> It could also contain a run-all-tests target to increase the similarity with
> the build.xml files of the other Tigris projects. I will make an attempt at
> creating the /trunk/build.xml.

Where does this file live in the Eclipse checkout directory structure?
 It needs to live in a project, not directly in the <workspace> root
directory.

> Unless you fix this, Dave, I will fix it for the release 0.25.5 to avoid
> having to change the 10 or more other Tigris projects that relies on having
> the files in argouml/build to be built. After the 0.26 release we could
> revisit this again.

If things are required to stay unchanged until after 0.26, why did we
make ourselves endure two rounds of massive changes?  That's a huge
waste of time.

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to