Tom Morris wrote:
On Tue, May 6, 2008 at 12:01 PM, Linus Tolke <[EMAIL PROTECTED]> wrote:

  
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.
    

If we are going to use <workspace>/argouml/build, we'll need to create
an Eclipse project called "argouml" to hold this (or perhaps move
argouml-build to argouml).

  
Why? I assume that this directory will only be referenced via Ant build. These are allowed to go out of the workspace project paths, AFAIK...
Another thing is that anyone who is using the Ant build even in eclipse style checkouts should consider using the command line for things such as executing the compile, package, run and tests targets. These targets within eclipse are available via launch configurations...

(...)

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

Reply via email to