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). > 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. Of course the disadvantage to having multiple distributed copies of hardcoded path names is that the next time we change things we'll have to make sure we find all the various places the refer to the location that has changed. It would be useful to add some comments to the build.xml and properties files that the use of properties is forbidden/discouraged (depending on what you decide), because introducing properties to parameterize things will be a natural mistake for future editors to make. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
