Re: [Asterisk-java-users] pre-packaged jars

[Stefan R. <sr...@re...>]

On Wed, 2005-03-30 at 13:13 -0600, Alex Malinovich wrote:
> On Tue, 2005-03-22 at 22:59 +0000, Stefan Reuter wrote:
> --snip--
> > The dependency on commons-lang should be removed in latest CVS. I am no=
t
> > aware on a dependency of commons-logging on commons-lang.
>=20
> At the time that I was building the packages, there was a commons-lang
> function (something similiar to toString, but I forget the exact name)
> that was being called inside commons-logging.

I grepped the source code of commons-logging 1.0.4 for the string
"commons.lang" and found no match. Therefore I suppose recent versions
of commons-logging do no longer depend on commons-lang.

> > I will look at the code again when i am back home next week and decide =
if
> > its possible to borrow the stuff for switching the logging api between =
jdk
> > and log4j and remove that dependency as well.
>=20
> I don't know if there's any simple way to do this. For test, the logging
> functionality is definitely useful. However, when it comes time to
> distribute the program, having to add two extra dependencies that will
> NEVER actually be used is kind of frustrating.

Sure I understand your concerns. After further investigation I think the
easiest way to go is to use a very thin wrapper around commons-logging's
LogFactory that determines via reflection if the commons-logging classes
are available. If they are available on the classpath a commons-logging
Log object (in fact a proxy for it) will be returned otherwise a NullLog
will be returned that does nothing.
So we will still have a compile time dependency on commons-logging but
at runtime logging is just switched off if commons-logging is not
available.
Will this change help you?

> So far, I've had very positive experiences with the library. The
> application that I'm using it in has made it up to v0.97d and has been
> stable for over a week. (We use it all day every day during the week
> here at the office.)

Thats nice to hear and makes me more confident of providing a non-crappy
release candidat :)
r
> I have also received approval from my company to release the
> publicly under the GPL. As soon as I have some time to clean up the code
> and put in appropriate GPL blurbs in all the source I'm going to look at
> getting the project put up on sourceforge for continued development.

When you have more information available on that let us now - it will be
the first open source software using Asterisk-java i know of.

> At that point, I would be VERY interested in having release candidates
> available for asterisk-java so that I can easily say something like,
> v0.97d depends on asterisk-java rc1, v1.0 depends on asterisk-java rc3
> (or 0.2 rc1, etc.).

Sure. I will try my best to provide it asap. I will change the logging
dependency as described above and start packaging.
Did you have a look at the maven built snapshot releases on
http://maven.reucon.com/maven/asterisk-java/distributions/ ?

=3DStefan