You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Niclas Hedhman <ni...@hedhman.org> on 2004/03/28 21:06:40 UTC
Finally!
Gang,
avalon-excalibur FINALLY builds from scratch, with a single
maven multiproject:install
1. Everything in avalon-excalibur builds! Including ECM, compatibility, and
unit tests.
2. All intra-excalibur dependencies are set to the current version. No
excalibur downloads required for build.
3. Everything is updated to avalon-logkit ver 2.0. This required a potential
incompatibility in Fortress ContextManager.java, where Log4JConf were used in
a catch() clause, which I bluntly removed, and the fallback is to a LogKit
logger instead. (Anton, is that OK?)
4. All unit tests pass, except ONE, DefaultDOMHandlerFactoryTestCase in
xmlutil. I have been tinkering with the code, but can't get the namespace to
work. Help appreciated. Meanwhile, it doesn't fail on that error.
5. No more cyclic dependencies.
Please note that avalon-logkit needs to be built before excalibur;
cd avalon-logkit
maven jar:install
One major step and heaps of tiny changes had to be made to make this at all
possible, without breaking anything.
I have copied (with history) avalon/fortress to avalon-excalibur/fortress, and
restructured the content to remove these endless cross/cyclic dependencies,
and cvs-removed avalon/fortress.
Anyone having a problem with the changes required to make this possible, feel
free to roll back and make a build system that
1. Requires a single command per cvs module, 42 build commands are not
workable.
2. Builds under Gump without failures.
3. Solves the cross-dependency between "avalon" and "avalon-excalibur".
4. Solve the cross/cyclic dependencies within the Fortress package.
I still have more work to do, mainly
1. Create/validate equally simple system for other build targets/goals.
2. Make sure Gump works, as soon as the Gump folks gives thumbs up that the
recent problems has been solved.
3. Translate any remaining xdocs from forrest...
Any problems, please report ASAP.
Niclas
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Finally!
Posted by Stephen McConnell <mc...@apache.org>.
Niclas Hedhman wrote:
> Gang,
>
> avalon-excalibur FINALLY builds from scratch, with a single
> maven multiproject:install
Just completed a build of all of excalibur!
BUILD SUCCESSFUL
Total time: 7 minutes 36 seconds
Finished at: Mon Mar 29 12:52:18 CEST 2004
:-)
--
|------------------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org/merlin |
| http://dpml.net/merlin/distributions/latest |
|------------------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Finally!
Posted by Berin Loritsch <bl...@d-haven.org>.
Niclas Hedhman wrote:
> On Monday 29 March 2004 21:24, Berin Loritsch wrote:
>
>>The purpose of this was to allow Fortress to work with Jog4J or LogKit.
>>There should be the ability to use a Log4J config file or a LogKit config
>>file. We had a demand to support more than one logger, and as much work as
>>could be done to support was done.
>
>
> Ok.
> What I didn't understand was that the class in question was ONLY used inside a
> catch() clause. To me that seems a bit odd (I never use Exception as
> 'normal-path'), indicating that Log4J manage to get setup elsewhere.
>
> Have any takes on that?
>
> Niclas
>
> P.S. Sorry for not digging into Fortress all the way...
No need to be sorry.
The way it was set up was to try to use the LogKit config first. The thing is
that Log4J config is bad XML if namespaces are enabled on the parser--causing
the exception. If I recall correctly, we tried to examine the XML to determine
the system we should be using.
Yes, I agree that it is a hack, but it is what we had to do by consequence, not
design.
If there is a better way to determine the config file then by all means use it.
I personally use LogKit most of the time, so I am not as familiar with the Log4J
fallback mechanism. I just know why it was added, and I applied a patch that
another developer submitted--and they confirmed it worked. To that end I was
satisfied with it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Finally!
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Monday 29 March 2004 21:24, Berin Loritsch wrote:
> The purpose of this was to allow Fortress to work with Jog4J or LogKit.
> There should be the ability to use a Log4J config file or a LogKit config
> file. We had a demand to support more than one logger, and as much work as
> could be done to support was done.
Ok.
What I didn't understand was that the class in question was ONLY used inside a
catch() clause. To me that seems a bit odd (I never use Exception as
'normal-path'), indicating that Log4J manage to get setup elsewhere.
Have any takes on that?
Niclas
P.S. Sorry for not digging into Fortress all the way...
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Finally!
Posted by Berin Loritsch <bl...@d-haven.org>.
Niclas Hedhman wrote:
> Gang,
>
> 3. Everything is updated to avalon-logkit ver 2.0. This required a potential
> incompatibility in Fortress ContextManager.java, where Log4JConf were used in
> a catch() clause, which I bluntly removed, and the fallback is to a LogKit
> logger instead. (Anton, is that OK?)
The purpose of this was to allow Fortress to work with Jog4J or LogKit. There
should be the ability to use a Log4J config file or a LogKit config file.
We had a demand to support more than one logger, and as much work as could be
done to support was done.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org