Re: [CVS] How to compile Avalon/Excalibur (Bug in build system?)

Peter Donald <[email protected]>
Newsgroups gmane.comp.jakarta.avalon.apps.devel
Message-ID <200212120854.30962.peter__43698.3321946629$1039645392@realityforge.org>
Can someone take out time from the new bike sheds and courts of law to fix 
this?

On Wed, 11 Dec 2002 07:34, Peter Donald wrote:
> Hi,
>
> It looks like 1, 2 and 3 are bugs in build system. Thanks for telling us -
> could someone fix these up?
>
> On Wed, 11 Dec 2002 04:58, Olaf Bergner wrote:
> > Hi,
> >
> > I solved my problems, having successfully compiled Excalibur. Just a few
> > hints for people having similar problems (or am I the only one who is
> > that stupid?):
> >
> > 1) In the top-level ant.properties(.sample) file the version numbers of
> > the Xerces and Xalan jar files have to be updated to the ones found under
> > jakarta-avalon/tools/lib.
> >
> > 2) The property avalon.framework.home has to be changed from
> > (...)/jakarta-avalon/build/lib to (...)/jakarta-avalon/target/lib.
> >
> > 3) Using ant 1.5.1 I got an error complaining about an incorrect
> > "zipgroupfileset" element nested in a jar task that is part of the
> > "build.xml" under (...)/fortress. I changed it to "zipfileset", ommitting
> > the "group" part only to get a complaint about the "destfile" attribute.
> > Though the ant docs state that "destfile" is supported, I changed it to
> > "jarfile" and it worked like a charm.
> >
> > [4) I found out that - at least under Windows - you cannot use symbolic
> > links in ant.properties files :( ]
> >
> > Items 2 and 3 might hint at possible bugs in the build system though I am
> > not sure how much of it might be ant version dependant.
> >
> > Anyways, thanks for a great framework,
> >
> > Olaf
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Olaf Bergner [mailto:[email protected]]
> > > Gesendet: Dienstag, 10. Dezember 2002 17:26
> > > An: Avalon User List
> > > Betreff: [CVS] How to compile Avalon/Excalibur
> > >
> > >
> > > Hi,
> > >
> > > I have been quietly following discussions on this list for a few weeks,
> > > striving to port a little pet app of mine to (preferably) Fortress.
> > > Recognizing that the whole Avalon/Excalibur project seems to undergo a
> > > complete overhaul (or should this be a permanent situation?;)) I
> > > decided on
> > > fetching the sources via CVS, the more so since Fortress/Merlin
> > > are not yet
> > > released.
> > > Unfortunately, I got stuck while trying to compile
> > > "jakarta-avalon-excalibur". I am not a Java expert, much less an
> > > ant expert
> > > but I understand that the ant scripts that come with the sources seem
> > > to assume a certain directory layout for additionally needed packages
> > > etc. I have gambled a bit with the ant.properties file but until now to
> > > no avail. The java compiler keeps complaining about missing class
> > > definitions, most notably those pertaining to the *.extension.*
> > > package. What I did was creating a top-level directory "CVS-Modules"
> > > and checking out
> > > jakarta-avalon, jakarta-avalon-excalibur and
> > > jakarta-avalon-logkit into it,
> > > so as to have all required sources neatly combined under one common
> > > directory. But this failed to work out as expected.
> > > So I would like to know whether there is a better directory layout, or
> > > how to adapt the ant.properties file so as to compile Excalibur?
> > >
> > > Any help would be greatly appreciated,
> > >
> > > Olaf
> > >
> > > Olaf Bergner
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <mailto:[email protected]>
> > > For additional commands, e-mail:
> > > <mailto:[email protected]>

-- 
Cheers,

Peter Donald
---------------------------------------------------------
Clarke's Third Law: "Any technology distinguishable from 
magic is insufficiently advanced".
---------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.