Hello Dave!
Yes, this is one of the probably several more things that has not yet been
taken care of.
I would like to solve this in a more Eclipse-like manor, removing the
build2.sh and build2.bat and replacing them with a build configuration all
running without the ArgoUML-provided ant. I tried to solve it last night but
didn't have time to finish it.
Can you wait for me, or do you want to solve it yourself? I could also
commit your fix and stick with that until I eventually get back to this
again. What do you think? What do you think Michiel?
/Linus
2008/2/24, Dave T <[EMAIL PROTECTED]>:
>
> Hi Linus,
>
> The documentation didn't build for me on an eclipse style check-out
> using build2.sh or build2.bat. I assume this was as a result of the
> restructuring.
>
> The path to the eclipse-ant-build.properties in
> argouml.documentation/build2.sh[/.bat] was wrong, which was an easy fix,
> but it also looked like ${argo.tools.lib} and ${argo.build.dir} were not
> defined *anywhere* in the argouml-app and argouml-documentation
> projects!
>
> The attached patch fixes these problems for me, to make the
> documentation build successfully. I've defined the build dir to be
> 'build', at the same level as the eclipse project folders. I have not
> tested the documentation build launched from within eclipse (is there
> one? - if so, how do I start it?).
>
> Regards,
>
> Dave
>
> P.S. Did we reach a conclusion on a common directory naming system for
> the two types of check-out? It would reduce the chance of a fix in one
> build breaking something in another build.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
