[sip-comm-dev] [MacOSX] Sparkle and updatechecker conflict


#1

Hi,

I noticed that on the MacOSX packages, both sparkle and the updatechecker plugins propose an update at startup. The autoupdater is however disabled (i.e. line removed from the felix properties) when Sparkle is available at build time. Isn't the felix properties file looked up at each startup, or is it cached somewhere by the system?

The updatechecker.jar is however still included in the Mac package, I guess that if I remove it I'll get an exception at execution time?

What would be the best way to handle that?

Cheers,

···

--
Romain KUNTZ
kuntz@lsiit.u-strasbg.fr
LSIIT - Networks and Protocols Team
http://clarinet.u-strasbg.fr/~kuntz/

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


#2

Hey Romain,

Removing it from felix.client.run.properties should be enough not to
load it on start up. However, it would still run if you distribute it's
jar and if you haven't been deleting your felix cache since the times
the plugin was still active on mac.

In other words, we'd need to stop delivering the version update plugin
in order to resolve the conflict.

Cheers
Emil

Romain KUNTZ написа:

···

Hi,

I noticed that on the MacOSX packages, both sparkle and the
updatechecker plugins propose an update at startup. The autoupdater is
however disabled (i.e. line removed from the felix properties) when
Sparkle is available at build time. Isn't the felix properties file
looked up at each startup, or is it cached somewhere by the system?

The updatechecker.jar is however still included in the Mac package, I
guess that if I remove it I'll get an exception at execution time?

What would be the best way to handle that?

Cheers,

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


#3

Removing it from felix.client.run.properties should be enough not to
load it on start up. However, it would still run if you distribute it's
jar and if you haven't been deleting your felix cache since the times
the plugin was still active on mac.

Ok, I sometime run SC with from ant, that's why my cache is not coherent with the macosx package.

In other words, we'd need to stop delivering the version update plugin
in order to resolve the conflict.

Ok, then I'll add a rule in the build.xml to remove the updatechecker.jar when creating the macosx package with sparkle support.

Cheers,
romain

···

On 2008/09/11, at 11:27, Emil Ivov wrote:

Romain KUNTZ написа:

Hi,

I noticed that on the MacOSX packages, both sparkle and the
updatechecker plugins propose an update at startup. The autoupdater is
however disabled (i.e. line removed from the felix properties) when
Sparkle is available at build time. Isn't the felix properties file
looked up at each startup, or is it cached somewhere by the system?

The updatechecker.jar is however still included in the Mac package, I
guess that if I remove it I'll get an exception at execution time?

What would be the best way to handle that?

Cheers,

---------------------------------------------------------------------
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
LSIIT - Networks and Protocols Team
http://clarinet.u-strasbg.fr/~kuntz/

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