When building sarosServer from Source I receive the following error-message
$ ./gradlew sarosServer
Task :buildSrc:compileJava UP-TO-DATE
Task :buildSrc:compileGroovy NO-SOURCE
Task :buildSrc:pluginDescriptors UP-TO-DATE
Task :buildSrc:processResources UP-TO-DATE
Task :buildSrc:classes UP-TO-DATE
Task :buildSrc:jar UP-TO-DATE
Task :buildSrc:assemble UP-TO-DATE
Task :buildSrc:pluginUnderTestMetadata UP-TO-DATE
Task :buildSrc:compileTestJava NO-SOURCE
Task :buildSrc:compileTestGroovy NO-SOURCE
Task :buildSrc:processTestResources NO-SOURCE
Task :buildSrc:testClasses UP-TO-DATE
Task :buildSrc:test NO-SOURCE
Task :buildSrc:validatePlugins UP-TO-DATE
Task :buildSrc:check UP-TO-DATE
Task :buildSrc:build UP-TO-DATE
FAILURE: Build failed with an exception.
What went wrong:
A problem occurred configuring project ':saros.eclipse'.
Failed to notify project evaluation listener.
Could not initialize class com.diffplug.gradle.FileMisc
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at https://help.gradle.org
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
BUILD FAILED in 2s
As an FYI if anybody to avoid any confusion: You do not need the Saros Server to use Saros.
The server you need to use Saros is an XMPP server. You can either use our XMPP server (
saros-con.imp.fu-berlin.de) or host your own (as described on our website).
The Saros Server is a separate component that works as session host. The feature is meant to allow for longer living sessions with switching participants (i.e. to avoid the session ending because the user that started the session had to leave). But it is not necessary to use Saros.
The name of the component might have lead to confusion as the concept of an
XYZ Server is used differently by other applications, often meaning the server needed to use
XYZ. So we are thinking about renaming the component to avoid such confusion in the future and will add a note the server description on our website.
I just wanted to clarify it in general. :relaxed:
We need the Server in order to keep everyone up to date with the latest version.
Saros is generally not meant as a replacement for a version control system (like git) as it makes it hard to track changes over longer periods of time. But, if you still want to use it for code synchronization, don't let me keep you. :wink:
@nudelchef Are you still having issues with building the server?
Hi @kiwikern , thanks for trying our IntelliJ alpha.
I wanted to try out the plugin in Webstorm, but I found it's officially disabled for other distributions than IntelliJ.
It is currently disabled because we assume that there are subtle differences in the JetBrains IDEs. But in general, the plugin should be compatible with the other IDEs. If you try it, I would love to hear about your experiences (it would help to provide the plugin for all IntelliJ IDEs in the future).
Do I have to rebuild the project myself to allow Webstorm to work or can this be easily changed in the build artifact?
You can either:
Add the following lines to saros.intellij.zip/Saros/lib/saros.intellij.jar/META-INF/plugin.xml (you have to extract and re-zip the files) :
Or you use one of our nightly builds (not necessarily stable) which are installable in all IDEs. In order to find such a build, you can choose one build in our history (e.g. this).
However, when using modified/nightly builds, please make sure that all of the session participants are using the same modified/nightly plugin version. In case you find a bug, please mention your modifications or the nightly version. BR
now I get the following error starting the server:
INFORMATION: Loading providers for file [classpath:META-INF/extension.providers]
DEBUG 16:01:52,894 [main] (XMPPConnectionService.java:424) started Socks5 proxy on port: 41827 [listening on all interfaces]
DEBUG 16:01:52,898 [main] (XMPPConnectionService.java:441) using autodetected addresses: [192.168.99.15, fe80:0:0:0:24c9:9e5a:276e:6d35%eth0]
DEBUG 16:01:52,912 [main] (XMPPConnectionService.java:384) new connection state == CONNECTING
ERROR 16:01:53,702 [main] (XMPPConnectionService.java:386) new connection state == ERROR
SASL authentication DIGEST-MD5 failed: not-authorized:
DEBUG 16:01:53,714 [saros-XMPPContactService-ContactsThread] (XMPPContactsService.java:432) updated null - NOT_CONNECTED
DEBUG 16:01:53,859 [main] (XMPPConnectionService.java:384) new connection state == NOT_CONNECTED
Exception in thread "main" java.lang.NullPointerException
@nudelchef I just tried it with the most recent nightly and I am able to start the server without an issue. I am using the default command
java -Dsaros.firstname.lastname@example.org -Dsaros.server.password=1234 -jar saros.server.jar (replacing the placeholder credentials) given in the guide for the Saros server on our website.
Are you using our XMPP server (
saros-con.imp.fu-berlin.de) or a different server?
7777(no idea whether there is a specific reason for it). In Saros/I and the server, you currently don't have any way of accessing these settings.
Did somebody fixed the issue that you cant reconnect to the server until it was restarted or should I open a Issue page on Github?
No, I don't think anybody has had a look at that yet. We are working with limited resources and the Server is somewhat of a lower priority.
Opening an issue for it would still be appreciated so that we can keep track of it, but I can't promise that we will get around to fixing it in the near future.