Hi Linus,
When I first checked out the ArgoUML project months ago, I did it using
the .psf file, but I couldn't get eclipse to work (have since solved the
problem). Anyway, I was still able to do a successful build without
starting eclipse, using build2.bat from the windows command prompt. The
bat file was an alternative method for building argouml, and proved very
useful. It was evidently a messy setup because I saw special magic to
make the build work with the files in different directory names than a
command-line check-out of trunk/.
My ideal scenario (and I think the easiest to understand/maintain) would
be for a 'command line check-out' and an 'eclipse .psf check-out' to
result in the exact same set of files on disc, with the exact same
directory names and all. That way you could use either the command line
(build.sh/bat) *or* eclipse to build that same working copy. If one
tool wasn't working, you could try the other. No ant magic with special
build.properties files would be needed any more, as the files would
always be in the same place relative to one another. I think that this
could be achieved for the main argouml application by renaming the src/*
directories to the same names as the project names they are given in
eclipse, i.e.
src/app -> src/argouml-app
src/infra -> src/argouml-core-infra
src/model -> src/argouml-core-model
src/model-euml -> src/argouml-core-model-euml
src/model-mdr -> src/argouml-core-model-mdr
Then, src/build.* would have move to (presumably)
src/argouml-app/build.*. The directory src/ would contain only
directories, no files, so a src/ check-out would be no different to
separate check-outs of the directories below src/.
As for the documentation project, I'm not sure how this would best fit,
since it currently sits one level up in the repository, but when checked
out through the .psf file, it sits at the same level as the other source
code projects. Perhaps it too could be moved to within src/ in the
repository, i.e.
documentation -> src/argouml-documentation
Or even (a bit more radical) we could ditch the src/ level altogether,
and just have all of the directories straight under trunk, i.e.
src/app -> argouml-app
src/infra -> argouml-core-infra
src/model -> argouml-core-model
src/model-euml -> argouml-core-model-euml
src/model-mdr -> argouml-core-model-mdr
documentation -> argouml-documentation
[this would mean more unnecessary check-outs of www/ and though!]
Currently, the project will only build using the tool it was checked out
with (command line or eclipse). My hope was that we could one day use
either tool on a working copy, whichever way it was checked out, using
the same configuration files without any magic.
Does this make sense? To me it seems a sensible way forward, but my
experience of the argouml project is minimal so far. I guess I'm
frustrated having spent a good deal of time trying to understand how
this all hangs together, and want to prevent others from going through
this (in my opinion) unnecessary task in the future.
Regards,
Dave
On Sat, 1 Mar 2008 08:53:56 +0100, "Linus Tolke" <[EMAIL PROTECTED]>
said:
> 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]
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
