Hi Linus, Setting basedir=".." means that it is much easier to reference the subprojects and tools dir, simply by appending their name to the basedir. This was chosen only because it seemed the simplest way at the time. I can see how it might confuse things a little.
The alternative is to put "../" at the front of the other paths, or have them defined in the one of the .properties files. I don't mind which way it is done, we British would say it is 'Six of one and half a dozen of the other'. So if you can see a way to improve things, please go ahead. Where is the nightly build script actually kept, and where/how does it run? Perhaps I can replicate the setup and help fix it. Regards, Dave On Fri, 25 Apr 2008 00:25:29 +0200, "Linus Tolke" <[EMAIL PROTECTED]> said: > Hello Dave! > > I think I have a solution for the junit tests in the nightly build. I > will > let it run and examine the result tomorrow. > > Since the nightly build uses the <ant> function to call other ant > targets, > the change of basedir from "." to ".." caused a lot of problems and > requires > a lot of changes. > > Could we change back to basedir="." and use that throughout? > > If anyone is contemplating writing style guides for ant files, I suggest > forbidding anything but basedir=".". > > /Linus > > 2008/4/21 Linus Tolke <[EMAIL PROTECTED]>: > > > Great work Dave! > > > > I had a quick look at the nightly build and tried to move around some > > paths. It didn't work immediately so I will have to spend some more time on > > it. > > > > /Linus > > > > > > 2008/4/20, Dave Thompson <[EMAIL PROTECTED]>: > > > >> Hi All, > >> > >> ~~~~ > >> Flag day morning is a bright and cheerful morning. Children play in a > >> green meadow, as the warm radiant sun beams down. A yellow butterfly > >> flutters up from the daisies in a burst of excitement, while the > >> childrens' mother smiles, as she carries a tray of freshly made ginger > >> ale across the lush grass. The patriotic sound of trumpets fills the > >> air as a large flag is hoisted up a newly painted pole... > >> ~~~~ > >> > >> Ok, back to the point. The SVN repository has been restructured. You > >> can resume your work. The main changes you will see are: > >> > >> trunk/src/app -> trunk/src/argouml-app > >> trunk/src/infra -> trunk/src/argouml-infra > >> trunk/src/model -> trunk/src/argouml-model > >> trunk/src/model-euml -> trunk/src/argouml-model-euml > >> trunk/src/model-mdr -> trunk/src/argouml-model-mdr > >> > >> This is to harmonise the directory names in working copies that have > >> been checked out either through SVN or through Eclipse .psf files (see > >> issue 4625). They are now the same. I've also modified a few (i.e. > >> most) of the build.<xml|sh|bat> files to make it all work. Most things > >> are now working again, including the documentation build. > >> > >> Getting back up and running > >> --------------------------- > >> Eclipse Users: > >> You will need to remove any of the above projects from your workspace, > >> and re-import the new argouml-core-projectset.psf file found at > >> http://argouml.tigris.org/psf/. Your working copy will look pretty > >> similar to before. If you take this opportunity to start a fresh > >> workspace, make sure you set it up with the right options. (I found that > >> I had to set Window > Preferences > Java > Installed JREs to 1.5.0xx > >> before argouml would build). If you get build errors, select all > >> projects, do a refresh, clean and rebuild. > >> > >> SVN Users: > >> Please delete your working copies, and re check-out from either: > >> http://argouml.tigris.org/svn/argouml/trunk/ (everything) > >> or > >> > >> http://argouml.tigris.org/svn/argouml/trunk/src/ (argouml src only) > >> and > >> http://argouml.tigris.org/svn/argouml/trunk/tools/ (argouml tools) > >> > >> New Stuff > >> --------- > >> Eclipse users can now perform a command line build if they import the > >> argouml-command-line-build-projectset.psf file. The new project > >> 'argouml-build' performs no function in Eclipse, it simply checks out > >> the right files to allow you to do a build from a command prompt: > >> > >> c:\workspace\argouml-build> set JAVA_HOME=c:\progra~1\Java\jdkXXXXX > >> c:\workspace\argouml-build> build run > >> > >> or > >> > >> [/home/me/workspace/argouml-build ]$ export JAVA_HOME=/x/y/z > >> [/home/me/workspace/argouml-build ]$ ./build.sh run > >> > >> Outstanding Tasks > >> ----------------- > >> Here's what's left outstanding, anyone else can pick these up if they > >> want to, before I get to them: > >> * The JUnit tests ('build tests') seem to run ok, but the report > >> generation fails. > >> * Check the nightly build. If it was already working, have surely > >> broken it now. > >> * Check the ability to work with external modules in both Eclipse an on > >> the command line. > >> > >> Regards, > >> > >> Dave > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
