On startup, exceptions are logged (see below), could there be a
classpath issue?

Can't load log handler "net.java.sip.communicator.util.FileHandler"
java.lang.ClassNotFoundException: net.java.sip.communicator.util.FileHandler
java.lang.ClassNotFoundException: net.java.sip.communicator.util.FileHandler
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.util.logging.LogManager$3.run(LogManager.java:357)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.loadLoggerHandlers(LogManager.java:344)
at
java.util.logging.LogManager.initializeGlobalHandlers(LogManager.java:909)
at java.util.logging.LogManager.access$900(LogManager.java:128)
at
java.util.logging.LogManager$RootLogger.getHandlers(LogManager.java:990)
at
net.java.sip.communicator.launcher.SIPCommunicatorJWS.main(SIPCommunicatorJWS.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.javaws.Launcher.executeApplication(Launcher.java:1809)
at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1750)
at com.sun.javaws.Launcher.doLaunchApp(Launcher.java:1512)
at com.sun.javaws.Launcher.run(Launcher.java:130)
at java.lang.Thread.run(Thread.java:662)
java.lang.NullPointerException
at
net.java.sip.communicator.plugin.pluginmanager.PluginManagerActivator.start(PluginManagerActivator.java:86)
at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1904)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1822)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1192)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:266)
at java.lang.Thread.run(Thread.java:662)

I haven't updated the Webstart-branch since I created it after FOSDEM14, so
it is quite outdated.

I don't know what's going on with the logger. Unfortunately I cannot look
into this now, as I don't have a dev-environment with me. If I would guess,
then it could be related to the renaming of SIP-Communicator to Jitsi (and
some corresponding package renamings), as we developed the Webstart code
back in the days of SIPComm.

Don't know anymore about the 1.4/1.5 stuff, I think this is also ancient
stuff for the launcher on Mac. Shouldn't be a problem to even change this to
1.6 now.

On startup, exceptions are logged (see below), could there be a classpath
issue?

Can't load log handler "net.java.sip.communicator.util.FileHandler"
java.lang.ClassNotFoundException: net.java.sip.communicator.util.FileHandler
java.lang.ClassNotFoundException: net.java.sip.communicator.util.FileHandler
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.util.logging.LogManager$3.run(LogManager.java:357)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.loadLoggerHandlers(LogManager.java:344)
at
java.util.logging.LogManager.initializeGlobalHandlers(LogManager.java:909)
at java.util.logging.LogManager.access$900(LogManager.java:128)
at
java.util.logging.LogManager$RootLogger.getHandlers(LogManager.java:990)
at
net.java.sip.communicator.launcher.SIPCommunicatorJWS.main(SIPCommunicatorJW
S.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.javaws.Launcher.executeApplication(Launcher.java:1809)
at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1750)
at com.sun.javaws.Launcher.doLaunchApp(Launcher.java:1512)
at com.sun.javaws.Launcher.run(Launcher.java:130)
at java.lang.Thread.run(Thread.java:662)
java.lang.NullPointerException
at
net.java.sip.communicator.plugin.pluginmanager.PluginManagerActivator.start(
PluginManagerActivator.java:86)
at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.jav
a:629)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1904)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1822)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1192)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:266)
at java.lang.Thread.run(Thread.java:662)

Should this change (and my change for Java version) be applied to master
or should it stay on the branch? Could you remember why it was
necessary, should this jar/@duplicate attribute be added to any other
JARs perhaps?

Once that is on master, could somebody with commit access please merge
the latest master into the branch:

git checkout webstart && git merge master && git push

and then I'll test and submit my pull request against that.

I don't know what's going on with the logger. Unfortunately I cannot look
into this now, as I don't have a dev-environment with me. If I would guess,
then it could be related to the renaming of SIP-Communicator to Jitsi (and
some corresponding package renamings), as we developed the Webstart code
back in the days of SIPComm.

Maybe the merge from master will fix this - Jitsi seems to work anyway
but it would be nice to make the console output clean.

Don't know anymore about the 1.4/1.5 stuff, I think this is also ancient
stuff for the launcher on Mac. Shouldn't be a problem to even change this to
1.6 now.

It doesn't appear to be something specific to WebStart - should this
build.xml change also be made directly on master?

Ok, I'm happy to re-submit, but if somebody can just clarify the top
level build.xml changes, apply them on master and sync the branch from
master then let me know so I can test against the latest code.