Hi!
-------- Original-Nachricht --------
> Datum: Wed, 16 Sep 2009 12:54:41 +0100
> Von: Dave Thompson <[email protected]>
> An: [email protected]
> Betreff: Re: [argouml-dev] More euml build stuff
--<snip>--
> Thanks for taking a look at this. I hope that the problems with the
> build.xml|bat|sh files can be sorted out.
I'm currently looking at those problems.
I have it working at the moment.
What I did: called the euml 'install' target from the
argouml-build build.xml file. Changed the argo.build.dir in
the euml build.xml to ${argo.root.dir}/src/argouml-build
Changed the copy task in the install task to flatten=true, so
the eclipse jars are copied directly to the argo build dir and
not to the lib etc subdirs.
> There may be some hang over
> from the time when I moved over the repository to use a separate
> argouml-build project. At this time, the euml things were in there (I
> could see them but they didn't work and were commented out if I recall).
Yeah, most of the stuff was outcommented, right...
> There were a lot of changes to the way things worked, but I did not
> apply the changes to the euml sections. That means the old build code
> if it's still there, could be the old way, or redundant, or even just
> plain wrong. The best bet is to try to copy how the other modules are
> built and keep things consistent I think. On the other hand, if you can
> see a better way of doing it, then feel free to improve it.
There are some things, I don't understand yet. In the argouml-build
build.xml file, the built jars are copied to the build directory.
The same functionality is in the module build-files? I guess from
a design standpoint, it might be better to just pass the build-dir
to the module build-files and let them decide what is required to
be copied to the argo-build-dir? But then, inheritAll is false in those
module build-file calls?
> Also remember that when linux builds the code, he does so from the
> argoumlinstaller project, which may call other targets that are not
> automatically called from the standard command line build. I'm not
> quite sure but it might be worth taking a look.
Don't know how this installer project works...
> As far as the final app goes, it's no problem to have two different
> installed shortcuts in the start menu on the windows installer (for
> example), to launch the two different variants of argouml. That way we
> could bundle and install one set of jars, without having two separate
> downloads.
I'm not sure if we need the additional shortcut? The euml version
would only be for folks who know exactly what they are doing, but
not for the regular user. Do those folks need a shortcut?
> Instinctively, I would try to discourage having two different variants
> of ArgoUML, even if it was set up as two launcher links, because
> typically, two different variants mean that each one might get half as
> much attention from developers and users. It also confuses people who
> don't know the difference.
It would be best, if those folks would not know about the euml version...
Are you still working on the build-stuff? Should I mail you my latest
modifications so you can reproduce my results?
Ciao,
Andreas
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2395507
To unsubscribe from this discussion, e-mail:
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email:
[[email protected]]
