[sip-comm-dev] [Attn: Package Maintainers] updated installers to use lib/bundles/log4j


#1

Hi guys,

This message concerns contributors maintaining installation packages for
SIP Communicator.

Yesterday, I moved log4j to a separate bundle so that we don't have to
include it in every package that uses it. Since it is not going to be
generated on every build (and there's no need for it to be), I've placed
it in sip-communicator/lib/bundles. However, this turns out to be
causing problems for some of the installers. I've tried to fix the
debian, fedora, linux-generic, generic, and windows. Could you please
test and let me know whether I've broken anything?

I didn't have to change the MAC OS X dmg builder (good job Romain!)
since it was properly importing all jars in lib/bundles with the
exception of the junit.jar. It might be a good idea for other
maintainers to follow suite and change their installers when they have
some time available.

Cheers
Emil

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hi Emil,

I quickly confirmed that the MacOSX package still works fine :slight_smile:

Romain

···

On 2007/07/11, at 7:30, Emil Ivov wrote:

Hi guys,

This message concerns contributors maintaining installation packages for
SIP Communicator.

Yesterday, I moved log4j to a separate bundle so that we don't have to
include it in every package that uses it. Since it is not going to be
generated on every build (and there's no need for it to be), I've placed
it in sip-communicator/lib/bundles. However, this turns out to be
causing problems for some of the installers. I've tried to fix the
debian, fedora, linux-generic, generic, and windows. Could you please
test and let me know whether I've broken anything?

I didn't have to change the MAC OS X dmg builder (good job Romain!)
since it was properly importing all jars in lib/bundles with the
exception of the junit.jar. It might be a good idea for other
maintainers to follow suite and change their installers when they have
some time available.

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Romain KUNTZ
kuntz@lsiit.u-strasbg.fr
Louis Pasteur University - Networks and Protocols Team

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Emil,

Emil Ivov wrote:

Hi guys,

This message concerns contributors maintaining installation packages for
SIP Communicator.

Yesterday, I moved log4j to a separate bundle so that we don't have to
include it in every package that uses it. Since it is not going to be
generated on every build (and there's no need for it to be), I've placed
it in sip-communicator/lib/bundles. However, this turns out to be
causing problems for some of the installers. I've tried to fix the
debian, fedora, linux-generic, generic, and windows. Could you please
test and let me know whether I've broken anything?

No need to worry anymore for the debian package, I gave it a try and everything works as expected.

I didn't have to change the MAC OS X dmg builder (good job Romain!)
since it was properly importing all jars in lib/bundles with the
exception of the junit.jar. It might be a good idea for other
maintainers to follow suite and change their installers when they have
some time available.

I also took some time to change that too! Thanks for the tip :slight_smile:

Martin

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net