Hello Dave!
Yes, it means that you build the eclipse style check out using the Eclipse
configurations. If Eclipse doesn't provide a command-line tool for building
using configurations then that is not possible.
I don't understand exactly what you mean with the same file structure. I
have thought that the Eclipse file structure, when importing from the team
project set files, is very flat. Can you please describe what can be done.
If it is just a case of changing the names, I see no problem in that so that
can be done immediately, especially for the documentation projects.
/Linus
2008/2/29, Dave T <[EMAIL PROTECTED]>:
>
> Hi Linus,
>
> Sorry for delayed reply, I just got back from a holiday with my family.
>
> So does this mean that I cannot build an eclipse style check-out from
> the command line any longer? I used to use build2 to do this. Perhaps
> I was using the scripts in a non-standard way.
>
> As I eluded to before, I think it would be better if both styles of
> check-out resulted in the same file structure, then cygwin+build.sh OR
> eclipse could be used to compile everything. Will this ever be
> possible? If so, I'm keen to help make it happen.
>
> Thanks for removing build2, it will make things simpler in the long run.
>
> Dave
>
> On Tue, 26 Feb 2008 14:24:58 +0100, "Linus Tolke" <[EMAIL PROTECTED]>
> said:
> > Hello Dave!
> >
> > I have now "fixed" this so that there are two new configurations to
> build
> > the defaulthtml and the pdf from within Eclipse. The build2.sh and
> > build2.bat are not used.
> >
> > /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]
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
