You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Robert McIntosh <ro...@bull-enterprises.com> on 2003/02/10 20:52:14 UTC
Fortress binary
I don't suppose anyone has a current Fortress or even an excalibur
binary? I can't get either to build from CVS (updated today).
The DefaultThreadPool won't compile when building excalibur and if I
just try to build Fortress the logger won't build. Seems each relies on
org.apache.log.* files (?).
Any help? I would really hate to start tagging things as a Component if
I don't have to use the old ECM.
Thanks,
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary
Posted by Berin Loritsch <bl...@apache.org>.
Robert McIntosh wrote:
> I don't suppose anyone has a current Fortress or even an excalibur
> binary? I can't get either to build from CVS (updated today).
>
> The DefaultThreadPool won't compile when building excalibur and if I
> just try to build Fortress the logger won't build. Seems each relies on
> org.apache.log.* files (?).
LogKit.
> Any help? I would really hate to start tagging things as a Component if
> I don't have to use the old ECM.
I've got one working if you need it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary
Posted by Robert McIntosh <ro...@bull-enterprises.com>.
Thanks Leif,
I was hoping to start fresh with Fortress on this new version of what
I'm doing, but I may as an interim go with ECM just so I can do my unit
testing and development.
- Robert
Leif Mortenson wrote:
> Robert McIntosh wrote:
>
>> Any help? I would really hate to start tagging things as a Component
>> if I don't have to use the old ECM.
>
>
> The ECM was actually modified several months ago so that you can use
> non Component
> "components" with the ECM. Take a look at the
> ExcaliburComponentManagerCreator class,
> which makes it very easy to use. Simply call getServiceManager rather
> than
> getComponentManager and you are ready to go. The goal is definitely
> to move away from
> the ECM, but it is still a powerful, stable, released container.
> While newer projects have been
> using Fortress, I am still using the ECM for several projects.
>
> Cheers,
> Leif
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary
Posted by Robert McIntosh <ro...@bull-enterprises.com>.
I got the ECMC working for now. Thanks for the pointer.
- Robert
Leif Mortenson wrote:
> Robert McIntosh wrote:
>
>> Any help? I would really hate to start tagging things as a Component
>> if I don't have to use the old ECM.
>
>
> The ECM was actually modified several months ago so that you can use
> non Component
> "components" with the ECM. Take a look at the
> ExcaliburComponentManagerCreator class,
> which makes it very easy to use. Simply call getServiceManager rather
> than
> getComponentManager and you are ready to go. The goal is definitely
> to move away from
> the ECM, but it is still a powerful, stable, released container.
> While newer projects have been
> using Fortress, I am still using the ECM for several projects.
>
> Cheers,
> Leif
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Robert McIntosh wrote:
> Any help? I would really hate to start tagging things as a Component
> if I don't have to use the old ECM.
The ECM was actually modified several months ago so that you can use non
Component
"components" with the ECM. Take a look at the
ExcaliburComponentManagerCreator class,
which makes it very easy to use. Simply call getServiceManager rather than
getComponentManager and you are ready to go. The goal is definitely to
move away from
the ECM, but it is still a powerful, stable, released container.
While newer projects have been
using Fortress, I am still using the ECM for several projects.
Cheers,
Leif
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary (success)
Posted by Leo Simons <le...@apache.org>.
How to take ant to the limit with avalon-excalibur
--------------------------------------------------
Set ${lib.dir} in ~/.ant.properties (and in ~/ant.properties to be safe)
to your central library location. It's in common use in many ant-based
projects.
There's a few more, like avalon-site.dir and jakarta-site.dir which you
can just set to ${lib.dir}/.. or something similar, as all that's
normally needed in that case is the contents of that module its lib/
dir. This is on the TODO for changing to make more sense though :D
Then, you want to scan some of excalibur's default.properties files for
properties ending in '.lib:
grep -o -P '^(.*).lib=' fortress/default.properties;
Change all those to ${lib.dir} as well.
To live on the edge, set ${build.lib} to point to ${lib.dir} as well,
and when you build a project, the jar ends up into your big repo dir.
I used to have a pretty big ~/.ant.properties. I pretty much ditched it
in favour of a local gump install though.
sample .ant.properties
----------------------
lib.dir = ~/repo/jars
build.lib = ${lib.dir}
avalon-site.dir = ${lib.dir}/..
jakarta-site.dir = ${lib.dir}/..
avalon-framework.lib=${lib.dir}
logkit.lib=${lib.dir}
excalibur-container.lib=${lib.dir}
excalibur-instrument.lib=${lib.dir}
excalibur-instrument-manager.lib=${lib.dir}
excalibur-i18n.lib=${lib.dir}
excalibur-event.lib=${lib.dir}
excalibur-sourceresolve.lib=${lib.dir}
excalibur-xmlutil.lib=${lib.dir}
excalibur-logger.lib=${lib.dir}
excalibur-datasource.lib=${lib.dir}
excalibur-pool.lib=${lib.dir}
excalibur-component.lib=${lib.dir}
excalibur-cache.lib=${lib.dir}
excalibur-testcase.lib=${lib.dir}
excalibur-monitor.lib=${lib.dir}
# list goes on for other projects.... :D
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary (success)
Posted by Robert McIntosh <ro...@bull-enterprises.com>.
Well, I have one big /lib directory where I keep all of my common
'stuff', and that is where logkit went, so I had to change the
default.properties files to point there instead of to avalon's
directories. I probably made it harder on myself than necessary though...
- Robert
Leo Simons wrote:
> Robert McIntosh wrote:
>
>> After changing several prop files, I got fortress to build. Thanks guys.
>
>
> If you have an insight as to how to make the stuff easier for the next
> person to try, please share (or patch!). Ant can be a bitch sometimes.
>
> cheers!
>
> - Leo
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary (success)
Posted by J Aaron Farr <ja...@yahoo.com>.
--- Leo Simons <le...@apache.org> wrote:
> Robert McIntosh wrote:
> > After changing several prop files, I got fortress to build. Thanks guys.
>
> If you have an insight as to how to make the stuff easier for the next
> person to try, please share (or patch!). Ant can be a bitch sometimes.
>
> cheers!
>
> - Leo
>
I'll chime in on this one...
The only issue I've had with building fortress (or other avalon projects) is
that the build expects you to have everything set up as in CVS. Yes you can
over ride the defaults, but that can still be a pain especially since the
dependencies are often on other unreleased code, so you might as well just
checkout the entire module and build it all. This works well, but that's a lot
to check out. Granted, Fortress hasn't had an official release yet, but when
it does I would hope that the source distribution doesn't require recreating
the CVS environment just to build. IMHO the perfect source distribution would
do one of the following:
(1) include the dependency jars in a /lib directory
(2) include a list of the dependancies with links
or even better
(3) download the dependencies if they don't already exist on the local
machine (kinda like maven).
I guess I'm talking more about building the eventual 1.0 source distribution
than the current CVS module. Even still, a build system that can download
would be nice (be it maven or ant "import-***" targets).
just my $0.02
jaaron
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary (success)
Posted by Leo Simons <le...@apache.org>.
Robert McIntosh wrote:
> After changing several prop files, I got fortress to build. Thanks guys.
If you have an insight as to how to make the stuff easier for the next
person to try, please share (or patch!). Ant can be a bitch sometimes.
cheers!
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary (success)
Posted by Robert McIntosh <ro...@bull-enterprises.com>.
After changing several prop files, I got fortress to build. Thanks guys.
- Robert
Robert McIntosh wrote:
> I don't suppose anyone has a current Fortress or even an excalibur
> binary? I can't get either to build from CVS (updated today).
>
> The DefaultThreadPool won't compile when building excalibur and if I
> just try to build Fortress the logger won't build. Seems each relies
> on org.apache.log.* files (?).
>
> Any help? I would really hate to start tagging things as a Component
> if I don't have to use the old ECM.
>
> Thanks,
> Robert
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary
Posted by Robert McIntosh <ro...@bull-enterprises.com>.
I'm working on it now :-)
Seems I had an old logkit. I just grabbed rc7.
- Robert
Leo Simons wrote:
> Robert McIntosh wrote:
>
>> I don't suppose anyone has a current Fortress or even an excalibur
>> binary? I can't get either to build from CVS (updated today).
>
>
> worksforme...anyway,
>
> http://cvs.apache.org/~leosimons/excalibur/
>
> it's not even an alpha release...just a snapshot.
>
>> The DefaultThreadPool won't compile when building excalibur and if I
>> just try to build Fortress the logger won't build. Seems each relies
>> on org.apache.log.* files (?).
>
>
> that's logkit. Checkout avalon-logkit next to avalon-excalibur, and
> build that first. Or override ${logkit.jar} to point at a reasonably
> recent logkit jar.
>
> this will be made easier :D
>
> cheers,
>
> - Leo
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress binary
Posted by Leo Simons <le...@apache.org>.
Robert McIntosh wrote:
> I don't suppose anyone has a current Fortress or even an excalibur
> binary? I can't get either to build from CVS (updated today).
worksforme...anyway,
http://cvs.apache.org/~leosimons/excalibur/
it's not even an alpha release...just a snapshot.
> The DefaultThreadPool won't compile when building excalibur and if I
> just try to build Fortress the logger won't build. Seems each relies on
> org.apache.log.* files (?).
that's logkit. Checkout avalon-logkit next to avalon-excalibur, and
build that first. Or override ${logkit.jar} to point at a reasonably
recent logkit jar.
this will be made easier :D
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org