Debian package updated

Hello devs,

I just updated the Debian package in the cvs repository. You
can 
generate the debian package with the "deb" target
from ant (ie "ant deb" 
  in the root directory of the project).

Here is the list of changes:
* OSGI implementation changed from Oscar to Felix:
   - Bundle are now deployed by reference in
     ~/.felix/sip-communicator.bin
   - Updated libs accordingly
* Dependancy added on alsa-oss so JMF can now use Alsa
* Removed Junit in Recommand section, because it is not
relevant for the
   user

Any volunteers here to test the package?

Cheers,
Martin

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi,

I've tested it. There are some exceptions when starting it
from the 
console, there are about the log files.

Can't load log handler
"java.util.logging.FileHandler"
java.io.IOException: Couldn't get lock for
./log/sip-communicator%u.log
java.io.IOException: Couldn't get lock for
./log/sip-communicator%u.log
        at
java.util.logging.FileHandler.openFiles(FileHandler.java:361
)
        at
java.util.logging.FileHandler.<init>(FileHandler.java:
207)
        at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ
e 
Method)
        at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(Native
ConstructorAccessorImpl.java:39)
        at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De
legatingConstructorAccessorImpl.java:27)
        at
java.lang.reflect.Constructor.newInstance(Constructor.java:2
74)
        at java.lang.Class.newInstance0(Class.java:308)
        at java.lang.Class.newInstance(Class.java:261)
        at
java.util.logging.LogManager$5.run(LogManager.java:784)
        at
java.security.AccessController.doPrivileged(Native Method)
        at 
java.util.logging.LogManager.initializeGlobalHandlers(LogMan
ager.java:776)
        at
java.util.logging.LogManager.access$900(LogManager.java:114)
        at 
java.util.logging.LogManager$RootLogger.getHandlers(LogManag
er.java:883)
        at java.util.logging.Logger.log(Logger.java:420)
        at java.util.logging.Logger.doLog(Logger.java:446)
        at java.util.logging.Logger.log(Logger.java:469)
        at
net.java.sip.communicator.util.Logger.logEntry(Logger.java:7
6)
        at 
net.java.sip.communicator.impl.configuration.ConfigurationAc
tivator.start(ConfigurationActivator.java:34)

There is some other issue - I cannot start it from the Icon
in the menu. 
just from the console. Will try to find the problem.

Martin André wrote:
> Hello devs,
>
> I just updated the Debian package in the cvs
repository. You can 
> generate the debian package with the "deb"
target from ant (ie "ant 
> deb"  in the root directory of the project).
>
> Here is the list of changes:
> * OSGI implementation changed from Oscar to Felix:
>   - Bundle are now deployed by reference in
>     ~/.felix/sip-communicator.bin
>   - Updated libs accordingly
> * Dependancy added on alsa-oss so JMF can now use Alsa
> * Removed Junit in Recommand section, because it is not
relevant for the
>   user
>
> Any volunteers here to test the package?
>
> Cheers,
> Martin
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Damian,

thanks for your feedback.

Damian Minkov wrote:
> Hi,
> 
> I've tested it. There are some exceptions when starting
it from the 
> console, there are about the log files.

Indeed the location where to store the log file cannot be
opened. The 
default location defines a log directory in the directory
from where the 
SIP Communicator is run. This is ok when the user retrieves
the source 
via cvs and runs the SC from the his sandbox, but in our
particular case 
we need to change this behavior.
Saying that, i'm not fully convinced it worths logging to a
file when 
the package is installed. This is useful for developers but
most of the 
users don't care about log files. What do you think?

> There is some other issue - I cannot start it from the
Icon in the menu. 
> just from the console. Will try to find the problem.

This works fine for me. Could you tell me what's inside your

/usr/share/applications/sip-communicator.desktop file?

Martin

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Martin André wrote:
> Indeed the location where to store the log file cannot
be opened. The 
> default location defines a log directory in the
directory from where 
> the SIP Communicator is run. This is ok when the user
retrieves the 
> source via cvs and runs the SC from the his sandbox,
but in our 
> particular case we need to change this behavior.
> Saying that, i'm not fully convinced it worths logging
to a file when 
> the package is installed. This is useful for developers
but most of 
> the users don't care about log files. What do you
think?
Yes users don't care about the log but we care  if someone
reports a 
problem the log is the only way investigating it. Its good
to have the 
logging to be switched off or on from the configuration. But
I think for 
this release we can just switch it on. 
> This works fine for me. Could you tell me what's inside
your 
> /usr/share/applications/sip-communicator.desktop file?
Here is my /usr/share/applications/sip-communicator.desktop

[Desktop Entry]
Encoding=UTF-8
Name=SIP Communicator
GenericName=SIP Communicator
Comment=VoIP and Instant Messaging client
Icon=/usr/share/pixmaps/sip-communicator.xpm
Type=Application
Categories=Application;Network;
Exec=sip-communicator
Terminal=false

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hello,

I found the problem with starting the sip-communicator from
menu.
I have some custom settings in my /etc/bash.bashrc so the
java found in 
the console is diffrent from those
found in the start script when starting from menu.
When starting from the menu actually the java found is gcj
which seems 
misses some classes like java.util.logging... and
sip-communicator stops with exception and I cannot see
anything.
Seems like do not work only in my configuration.

damencho

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hello,

Damian Minkov wrote:
> Martin André wrote:
>> Indeed the location where to store the log file
cannot be opened. The 
>> default location defines a log directory in the
directory from where 
>> the SIP Communicator is run. This is ok when the
user retrieves the 
>> source via cvs and runs the SC from the his
sandbox, but in our 
>> particular case we need to change this behavior.
>> Saying that, i'm not fully convinced it worths
logging to a file when 
>> the package is installed. This is useful for
developers but most of 
>> the users don't care about log files. What do you
think?
> Yes users don't care about the log but we care  if someone
reports a 
> problem the log is the only way investigating it. Its
good to have the 
> logging to be switched off or on from the
configuration. But I think for 
> this release we can just switch it on. 

I agree with this. I don't think it hurts having the log
file. We could 
easily ask users to send it over when experiencing problems
and it would 
be trickier to make them enable it if it has been disabled.


>> This works fine for me. Could you tell me what's
inside your 
>> /usr/share/applications/sip-communicator.desktop
file?
> Here is my
/usr/share/applications/sip-communicator.desktop
> 
> [Desktop Entry]
> Encoding=UTF-8
> Name=SIP Communicator
> GenericName=SIP Communicator
> Comment=VoIP and Instant Messaging client
> Icon=/usr/share/pixmaps/sip-communicator.xpm
> Type=Application
> Categories=Application;Network;
> Exec=sip-communicator
> Terminal=false
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Well that's strange, doesn't the package have a dependency
on sun's 
java? Given that gcj has long been the only debian
alternative for java, 
many people might be in the same situation.

Emil

Damian Minkov wrote:
> Hello,
> 
> I found the problem with starting the sip-communicator
from menu.
> I have some custom settings in my /etc/bash.bashrc so
the java found in 
> the console is diffrent from those
> found in the start script when starting from menu.
> When starting from the menu actually the java found is
gcj which seems 
> misses some classes like java.util.logging... and
> sip-communicator stops with exception and I cannot see
anything.
> Seems like do not work only in my configuration.
> 
> damencho
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Martin!

I just remembered that I wanted to comment on one point but
almost 
forgot to.

Martin André wrote:
>    - Bundle are now deployed by reference in
>      ~/.felix/sip-communicator.bin

I'd personally prefer this to be something like
~/.sip-communicator/plugins

We already have a ~/.sip-communicator directory so we'd
better use it 
for all the SIP Communicator stuff that needs to be in the
user home.

Besides, in the general case this directory would only be
used for user 
specific sip-communicator plugins so if a user needs to
modify her 
repository, she would first try to look for it in a
~/.sip-communicator 
like directory.

WDYT?

Emil



>    - Updated libs accordingly
> * Dependancy added on alsa-oss so JMF can now use Alsa
> * Removed Junit in Recommand section, because it is not
relevant for the
>    user
> 
> Any volunteers here to test the package?
> 
> Cheers,
> Martin
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net