Hi All,
Ok, I was able to get past the problem by overriding the dependancies for
logkit in project.xml with a CVS built one:
Index: project.properties
===================================================================
RCS file: /home/cvs/avalon/fortress/container/project.properties,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 project.properties
--- project.properties 9 Jun 2003 15:27:41 -0000 1.1.1.1
+++ project.properties 17 Jun 2003 12:24:42 -0000
@@ -9,3 +9,13 @@
# gump integration
project.name=avalon-fortress-container
+
+# ------------------------------------------------------------------------
+# M A V E N J A R O V E R R I D E
+# ------------------------------------------------------------------------
+maven.jar.override = on
+
+# -----------------------------------------------------------------------
+# Jars set explicity by path.
+# ------------------------------------------------------------------------
+maven.jar.logkit = ${basedir}/../../../avalon-logkit/build/lib/logkit.jar
As Leo pointed out in a previous email snapshots seem to be the way to go
for unreleased dependancies.
While the tests are still broken though, what should we do? Check in the
above? or fix the problem with one of the methods described below?
Any thoughts?
Cheers,
Marcus
On Tue, Jun 17, 2003 at 01:37:58PM +0200, Marcus Crafter wrote:
> Hi All,
>
> Hope all is well!
>
> Finally have Fortress building under JDK 1.3.1 using Maven, looks great.
>
> One test case is failing though, due to a missing class in logkit. The
> class in question is org.apache.log.util.Closeable, which from what I can
> tell hasn't yet made it into a release.
>
> Problem is, Excalibur-Logging references it in it's released version 1.0.1
> and the test case freaks because Excalibur-Logging can't find it:
>
> Testcase: testContextManager took 1.358 sec
> Caused an ERROR
> org/apache/log/util/Closeable
> java.lang.NoClassDefFoundError: org/apache/log/util/Closeable
> at
> org.apache.avalon.excalibur.logger.LogKitLoggerManager.dispose(LogKitLoggerManager.java:580)
>
> So, how do we fix this problem - Maven uses libraries from it's
> repository. Do we need a new release of logkit ? Can we tell Maven to use
> a local version ? or is there some other alternative which is better ?
>
> Cheers,
>
> Marcus
>
> --
> .....
> ,,$$$$$$$$$, Marcus Crafter
> ;$' '$$$$: Computer Systems Engineer
> $: $$$$: ManageSoft GmbH
> $ o_)$$$: 82-84 Mainzer Landstrasse
> ;$, _/\ &&:' 60327 Frankfurt Germany
> ' /( &&&
> \_&&&&'
> &&&&.
> &&&&&&&:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
