You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2002/04/02 11:55:49 UTC
Anyone able to build excalibur?
Hi,
sorry if this is a dumb question - I wasn't able to follow all the
discussions over the last weeks.
But is anyone able to build excalibur from scratch without big
modifications?
I delete the excalibur directory and made a fresh check-out.
Then I installed the commons-altrmi (jakarta-commons-sandbox), junit, jmx
package like they were referenced in the sample ant.properties file. I
renamed the ant.properties.sample file to ant.properites and corrected the
base-path. So everything should be fine...
But unfortunately during the build of the "all" package no SAX classes were
found. I fixed this by copying the xml-apis.jar to all/lib, but then next
errors occur.
So did I simply oversee something or is the build system not yet ready?
Carsten
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Anyone able to build excalibur?
Posted by Paul Hammant <Pa...@yahoo.com>.
Carsten,
I am going to optimistically estimate that all remaining issues will be
resoved in the next couple of days. Worst case scenario is four days.
Multiple people are trying to fix it & it will be a lot easier than you
say :-)
- Paul
>Hi,
>
>sorry if this is a dumb question - I wasn't able to follow all the
>discussions over the last weeks.
>
>But is anyone able to build excalibur from scratch without big
>modifications?
>I delete the excalibur directory and made a fresh check-out.
>
>Then I installed the commons-altrmi (jakarta-commons-sandbox), junit, jmx
>package like they were referenced in the sample ant.properties file. I
>renamed the ant.properties.sample file to ant.properites and corrected the
>base-path. So everything should be fine...
>
>But unfortunately during the build of the "all" package no SAX classes were
>found. I fixed this by copying the xml-apis.jar to all/lib, but then next
>errors occur.
>
>So did I simply oversee something or is the build system not yet ready?
>
>
>Carsten
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Anyone able to build excalibur?
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Jeff Turner wrote:
>
> Hmm.. well then the default assumption (all/defaults.properties) should
> be used. xalan.jar defaults to
> ../../jakarta-avalon/tools/lib/xalan-2.2.0-D13.jar
>
> Does that file exist? You don't perhaps have an old Avalon with a
> different xalan?
>
> The just-committed build.xml should check for it's presence now.
>
It exists and now it works.
Thanks
Carsten
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Anyone able to build excalibur?
Posted by Jeff Turner <je...@socialchange.net.au>.
On Tue, Apr 02, 2002 at 02:28:14PM +0200, Carsten Ziegeler wrote:
> >
> > Doh.. well it means it can't find xerces.jar at the default path
> > ../../jakarta-avalon/tools/lib/xerces-1.4.4.jar
> >
> Ehm, I think it's Xalan and not xerces.
Ah yes, thanks.. just updated build.xml to check for xalan.jar.
> > Do you have jakarta-avalon checked out in the same directory as
> > jakarta-avalon-excalibur? That's the default assumption.
> >
> Yes.
Hmm.. well then the default assumption (all/defaults.properties) should
be used. xalan.jar defaults to
../../jakarta-avalon/tools/lib/xalan-2.2.0-D13.jar
Does that file exist? You don't perhaps have an old Avalon with a
different xalan?
The just-committed build.xml should check for it's presence now.
--Jeff
> > I'm just about to commit a check for xerces.jar. This is just the sort
> > of feedback required :) Thanks a lot,
> >
> No problem, so know we need a check for xalan then :)
>
> Carsten
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Anyone able to build excalibur?
Posted by Jeff Turner <je...@socialchange.net.au>.
On Tue, Apr 02, 2002 at 10:14:43PM +1000, Jeff Turner wrote:
> I'm just about to commit a check for xerces.jar.
Btw, a 'cvs update' is all that's required to get this change. You'll
see the project.properties file reappear, but that's not important;
all the build.xml's will have a sticky 'depchecking' tag set. If you
ever want to go back to the head, the command is 'cvs update -A <files>'
--Jeff
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Anyone able to build excalibur?
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Jeff Turner wrote:
>
> On Tue, Apr 02, 2002 at 02:00:33PM +0200, Carsten Ziegeler wrote:
> >
> > Jeff Turner wrote:
> > >
> > >
> > > That would happen if the depchecking.sh didn't retrieve
> > > 'default.properties' in the Excalibur root. Could you check to see if
> > > it's there? All the files listed in depchecking.sh must be present
> > > (./default.properties is listed there).
> > >
> > Ah yes, it didn't work. It seems the leading ./ caused some problems on
> > windows.
>
> Didn't think of that.. will update the list.
>
Thanks!
> > OK, now I removed it and the update seems to work and I can now
> type "ant"
> > and, guess what, I get a class not found message
> "org.apache.xpath.XPathAPI"
> > in the "all" package.
>
> Doh.. well it means it can't find xerces.jar at the default path
> ../../jakarta-avalon/tools/lib/xerces-1.4.4.jar
>
Ehm, I think it's Xalan and not xerces.
> Do you have jakarta-avalon checked out in the same directory as
> jakarta-avalon-excalibur? That's the default assumption.
>
Yes.
> I'm just about to commit a check for xerces.jar. This is just the sort
> of feedback required :) Thanks a lot,
>
No problem, so know we need a check for xalan then :)
Carsten
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Anyone able to build excalibur?
Posted by Jeff Turner <je...@socialchange.net.au>.
On Tue, Apr 02, 2002 at 02:00:33PM +0200, Carsten Ziegeler wrote:
>
> Jeff Turner wrote:
> >
> >
> > That would happen if the depchecking.sh didn't retrieve
> > 'default.properties' in the Excalibur root. Could you check to see if
> > it's there? All the files listed in depchecking.sh must be present
> > (./default.properties is listed there).
> >
> Ah yes, it didn't work. It seems the leading ./ caused some problems on
> windows.
Didn't think of that.. will update the list.
> OK, now I removed it and the update seems to work and I can now type "ant"
> and, guess what, I get a class not found message "org.apache.xpath.XPathAPI"
> in the "all" package.
Doh.. well it means it can't find xerces.jar at the default path
../../jakarta-avalon/tools/lib/xerces-1.4.4.jar
Do you have jakarta-avalon checked out in the same directory as
jakarta-avalon-excalibur? That's the default assumption.
I'm just about to commit a check for xerces.jar. This is just the sort
of feedback required :) Thanks a lot,
--Jeff
> Thanks for your help so far Jeff.
>
> Carsten
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Anyone able to build excalibur?
Posted by Paul Hammant <Pa...@yahoo.com>.
Carsten,
>OK, now I removed it and the update seems to work and I can now type "ant"
>and, guess what, I get a class not found message "org.apache.xpath.XPathAPI"
>in the "all" package.
>
That is because we are all putting xalan in our Ant/lib. Vanilla Ant
doesnot have that....
Useful feedback.
- Paul
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Anyone able to build excalibur?
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Jeff Turner wrote:
>
>
> That would happen if the depchecking.sh didn't retrieve
> 'default.properties' in the Excalibur root. Could you check to see if
> it's there? All the files listed in depchecking.sh must be present
> (./default.properties is listed there).
>
Ah yes, it didn't work. It seems the leading ./ caused some problems on
windows.
OK, now I removed it and the update seems to work and I can now type "ant"
and, guess what, I get a class not found message "org.apache.xpath.XPathAPI"
in the "all" package.
Thanks for your help so far Jeff.
Carsten
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Anyone able to build excalibur?
Posted by Jeff Turner <je...@socialchange.net.au>.
On Tue, Apr 02, 2002 at 01:25:28PM +0200, Carsten Ziegeler wrote:
> Ok,
>
> I tried it again, removed my check-out directoy, made a clean checkout of
> excalibur
> and cd'ed into the directory and simply called "ant" (with installed ant
> 1.4.1).
The crucial bit is the 'source depchecking.sh' or equivalent. Without
that, it's the old system.
> So it seems I have to install a ant.properties first.
Yes, you'd have to with the old system, and maybe even with the new. At
least with the new system, you'd get a nice error message instead of
javac compile errors.
>
> Anyway, after modifying the depchecking.sh for windows and rerunning "ant",
> I get the
> following error:
>
> D:\sunshine\jakarta-avalon-excalibur\all\build.xml:158:
> java.io.FileNotFoundExc
> ption: D:\sunshine\jakarta-avalon-excalibur\all\depchecker.xml
That would happen if the depchecking.sh didn't retrieve
'default.properties' in the Excalibur root. Could you check to see if
it's there? All the files listed in depchecking.sh must be present
(./default.properties is listed there).
--Jeff
> Hmm, strange
>
> Carsten
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Anyone able to build excalibur?
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Ok,
I tried it again, removed my check-out directoy, made a clean checkout of
excalibur
and cd'ed into the directory and simply called "ant" (with installed ant
1.4.1).
The following message then appears:
compile:
[mkdir] Created dir:
D:\sunshine\jakarta-avalon-excalibur\concurrent\build\c
lasses
[javac] Compiling 10 source files to
D:\sunshine\jakarta-avalon-excalibur\co
ncurrent\build\classes
[javac]
D:\sunshine\jakarta-avalon-excalibur\concurrent\src\test\org\apache\
avalon\excalibur\concurrent\test\ReadWriteLockTestCase.java:10: cannot
resolve s
ymbol
[javac] symbol : class TestCase
[javac] location: package framework
[javac] import junit.framework.TestCase;
[javac] ^
[javac]
D:\sunshine\jakarta-avalon-excalibur\concurrent\src\test\org\apache\
avalon\excalibur\concurrent\test\ReadWriteLockTestCase.java:19: cannot
resolve symbol
So it seems I have to install a ant.properties first.
Anyway, after modifying the depchecking.sh for windows and rerunning "ant",
I get the
following error:
D:\sunshine\jakarta-avalon-excalibur\all\build.xml:158:
java.io.FileNotFoundExc
ption: D:\sunshine\jakarta-avalon-excalibur\all\depchecker.xml
Hmm, strange
Carsten
> -----Original Message-----
> From: Jeff Turner [mailto:jeff@snow.socialchange.net.au]On Behalf Of
> Jeff Turner
> Sent: Tuesday, April 02, 2002 1:19 PM
> To: Avalon Developers List
> Subject: Re: Anyone able to build excalibur?
>
>
> On Tue, Apr 02, 2002 at 01:06:43PM +0200, Carsten Ziegeler wrote:
> >
> > Jeff Turner wrote:
> > >
> > > Hi Carsten,
> > >
> > > The new build system was finished yesterday, and still needs testing,
> > > but I think even in it's untested state you'll have more success than
> > > with the old system. I can go from a fresh CVS checkout to having an
> > > avalon-excalibur.jar, by just typing 'ant' in the root. The external
> > > deps (jmx, altrmi) only need be specified if you want those
> components,
> > > which you won't if you're building for Cocoon.
> > >
> > Hmm, I did the same, just typed in "ant" but this resulted very soon
> > in some imports of "junit" classes which were not there. So I started
> > to check out all this jmx, altrmi stuff etc.
>
> There's now junit checks all over the place (Paul is keen on them;).
>
> > So for a usual build I don't have to renam the "ant.properties.sample"
> > to "ant.properties".
> >
> > > To try it, run 'source depchecking.sh' in the root.
> > >
> > ok, I forgot to tell a little thing: I'm using windows2k here...
>
> All that depchecking.sh does is 'cvs update -r depchecking <list of
> relevant files>'. If you can cut and paste that into cygwin or the
> bottom pane of WinCVS it should work.
>
>
> --Jeff
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Anyone able to build excalibur?
Posted by Jeff Turner <je...@socialchange.net.au>.
On Tue, Apr 02, 2002 at 01:06:43PM +0200, Carsten Ziegeler wrote:
>
> Jeff Turner wrote:
> >
> > Hi Carsten,
> >
> > The new build system was finished yesterday, and still needs testing,
> > but I think even in it's untested state you'll have more success than
> > with the old system. I can go from a fresh CVS checkout to having an
> > avalon-excalibur.jar, by just typing 'ant' in the root. The external
> > deps (jmx, altrmi) only need be specified if you want those components,
> > which you won't if you're building for Cocoon.
> >
> Hmm, I did the same, just typed in "ant" but this resulted very soon
> in some imports of "junit" classes which were not there. So I started
> to check out all this jmx, altrmi stuff etc.
There's now junit checks all over the place (Paul is keen on them;).
> So for a usual build I don't have to renam the "ant.properties.sample"
> to "ant.properties".
>
> > To try it, run 'source depchecking.sh' in the root.
> >
> ok, I forgot to tell a little thing: I'm using windows2k here...
All that depchecking.sh does is 'cvs update -r depchecking <list of
relevant files>'. If you can cut and paste that into cygwin or the
bottom pane of WinCVS it should work.
--Jeff
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Anyone able to build excalibur?
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Jeff Turner wrote:
>
> Hi Carsten,
>
> The new build system was finished yesterday, and still needs testing,
> but I think even in it's untested state you'll have more success than
> with the old system. I can go from a fresh CVS checkout to having an
> avalon-excalibur.jar, by just typing 'ant' in the root. The external
> deps (jmx, altrmi) only need be specified if you want those components,
> which you won't if you're building for Cocoon.
>
Hmm, I did the same, just typed in "ant" but this resulted very soon
in some imports of "junit" classes which were not there. So I started
to check out all this jmx, altrmi stuff etc.
So for a usual build I don't have to renam the "ant.properties.sample"
to "ant.properties".
> To try it, run 'source depchecking.sh' in the root.
>
ok, I forgot to tell a little thing: I'm using windows2k here...
> On Tue, Apr 02, 2002 at 11:55:49AM +0200, Carsten Ziegeler wrote:
> > Hi,
> >
> > sorry if this is a dumb question - I wasn't able to follow all the
> > discussions over the last weeks.
> >
> > But is anyone able to build excalibur from scratch without big
> > modifications?
> > I delete the excalibur directory and made a fresh check-out.
> >
> > Then I installed the commons-altrmi (jakarta-commons-sandbox),
> junit, jmx
> > package like they were referenced in the sample ant.properties file. I
> > renamed the ant.properties.sample file to ant.properites and
> corrected the
> > base-path. So everything should be fine...
> >
> > But unfortunately during the build of the "all" package no SAX
> classes were
> > found. I fixed this by copying the xml-apis.jar to all/lib,
> but then next
> > errors occur.
>
> Another bug.. the ../jakarta-avalon/tools/lib/xerces-1.4.4.jar we rely
> on doesn't contain org.xml.sax.* any more. I've just fixed it in the
> depchecking branch.
>
> > So did I simply oversee something or is the build system not yet ready?
>
> It's not in the CVS head. 'source depchecking.sh' and be our guinea pig
> :) After this, javac build failures should be a thing of the past.
>
>
Thanks,
Carsten
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Anyone able to build excalibur?
Posted by Jeff Turner <je...@socialchange.net.au>.
Hi Carsten,
The new build system was finished yesterday, and still needs testing,
but I think even in it's untested state you'll have more success than
with the old system. I can go from a fresh CVS checkout to having an
avalon-excalibur.jar, by just typing 'ant' in the root. The external
deps (jmx, altrmi) only need be specified if you want those components,
which you won't if you're building for Cocoon.
To try it, run 'source depchecking.sh' in the root.
On Tue, Apr 02, 2002 at 11:55:49AM +0200, Carsten Ziegeler wrote:
> Hi,
>
> sorry if this is a dumb question - I wasn't able to follow all the
> discussions over the last weeks.
>
> But is anyone able to build excalibur from scratch without big
> modifications?
> I delete the excalibur directory and made a fresh check-out.
>
> Then I installed the commons-altrmi (jakarta-commons-sandbox), junit, jmx
> package like they were referenced in the sample ant.properties file. I
> renamed the ant.properties.sample file to ant.properites and corrected the
> base-path. So everything should be fine...
>
> But unfortunately during the build of the "all" package no SAX classes were
> found. I fixed this by copying the xml-apis.jar to all/lib, but then next
> errors occur.
Another bug.. the ../jakarta-avalon/tools/lib/xerces-1.4.4.jar we rely
on doesn't contain org.xml.sax.* any more. I've just fixed it in the
depchecking branch.
> So did I simply oversee something or is the build system not yet ready?
It's not in the CVS head. 'source depchecking.sh' and be our guinea pig
:) After this, javac build failures should be a thing of the past.
--Jeff
> Carsten
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>