Excellent. Thanks for giving up your Saturday night to do this (and
especially for keeping us informed along the way).
The Eclipse builds ran perfectly and both ArgoEclipse and the ArgoUML
modules seem happy with the new structure (although I need a couple of
the ArgoEclipse .psf files where they include the ArgoUML projects).
The command line build works for building and running the app, but it
looks like it's missing the JUnit jar (or has a wrong reference)
because it spits out lots of complaints about not being able to find
assertTrue, assertEquals, etc when it tries to compile the tests. I'm
sure that's a simple fix, but I'm going to wait 'til morning to work
on it (if no one gets there ahead of me).
All I had to do to fix my Hudson CI server was change the target build
file from
...\src\build.xml
to
...\src\argouml-build\build.xml
and the place I look for JUnit results from
src/app/build/tests/reports/TESTS-TestSuites.xml
to
src/argouml-app/build/tests/reports/TESTS-TestSuites.xml
so perhaps that will be enough to fix the nightly builds as well.
Thanks again for a smooth transition.
Tom
On Sat, Apr 19, 2008 at 7:22 PM, Dave Thompson <[EMAIL PROTECTED]> wrote:
> 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]
