Me and Stefan have provided a bad solution, which introduce a placeholder class, just to get the injections to work. This is not pretty and do not solve the basic problem of these circular dependence chain. See discussion here: http://saros-build.imp.fu-berlin.de/gerrit/#/c/3033/
@MatthiasBohnstedt Indeed, I think I had a solution for this. I prepared a restructuring of the ui-project -- it took me about two full days, until I finally found a distribution of responsibilities that seemed easy to understand. I did this back in the days when I introduced the @BrowserFunction annotations, but I did not want to push any more patches then. I don't know when I will come around to take a look at this, hopefully by the end of this week ...
I don't see any error messages, and the required plugins are also there - so I'm not sure where else to look
I'm just downloading STS to take a look
@crispi: I created a "user" channel in Gitter https://gitter.im/saros-project/saros/user
i found an anoying issue with this plugin and i was wondering on how to fix it.
i am collaboratively working on a mod for minecraft but when i execute the gradlew batch file to setup and decomp the workspace it breaks his library and when he does it i see the errors.
i am collaboratively working on a mod for minecraft but when i execute the gradlew batch file to setup and decomp the workspace it breaks his library and when he does it i see the errors.
*it, in the meantime you can use basically any XMPP server.
Help svp
Help me please!!!
I cant connect to Saros, this is the Error message : "Could not connect to XMPP server"
(I'm french)
@JackboyPlay "like the project is on a server or something else": We call it Saros Server, see http://www.saros-project.org/ongoing-work (under "dormant work"). Feel free to get in touch if you're interested in furthering that development.
OK, the XMPP problem has to do with our build-server migration a while back. Changed the secondary host-name of the machine running the XMPP server, which said server did not take too well. This problem did not surface before probably because this was the first system reboot after the hostname change.
Hi, I would like to introduce a code of conduct in the saros project. The "Contributor Covenant" is very common, simple and contains all necessary information. What do you think?
@m273d15 Could you provide a way of setting the base path for the IntelliJ sandboxes through an environmental variable? The default option to use the build directory if no path is set is fine, but it really annoys me to always have to set up the settings for sandboxes again after cleaning the project.
http://saros-build.imp.fu-berlin.de/sarosDoc/interfacede_1_1fu__berlin_1_1inf_1_1dpp_1_1filesystem_1_1_i_folder.html Do we have an updated version of this ?
http://saros-build.imp.fu-berlin.de/sarosDoc/interfacede_1_1fu__berlin_1_1inf_1_1dpp_1_1filesystem_1_1_i_folder.html Do we have an updated version of this ?
I don't think so. You can try to create the current javadoc with ./gradlew javadoc, but my first try was not successful. Probably the configuration is not correct or we have errors in our documentation. We should fix it.
@m273d15 Would it be possible to cache a version of the google java formatter? Some format builds run more than 6 minutes: https://travis-ci.com/saros-project/saros/jobs/177809507
As others finish in about a minute, I would guess that the actual formatting should not take more than about 45 seconds. My guess would be that the download is inconsistent, which sometimes slows down the build unnecessary.
As others finish in about a minute, I would guess that the actual formatting should not take more than about 45 seconds. My guess would be that the download is inconsistent, which sometimes slows down the build unnecessary.
@tobous Yes, travis provides a caching mechanism for arbitrary directories. This should lead to a consistent download time.
It would be also possible to cache the gradle dependencies, but I never enabled this feature, because I was not sure how the invalidation mechanism works ... and we know
It would be also possible to cache the gradle dependencies, but I never enabled this feature, because I was not sure how the invalidation mechanism works ... and we know
There are only two hard things in Computer Science: cache invalidation and naming things.
We recently merged a large scale refactoring of the directory/package structure of the saros repository. This mail on our developer mailing list gives some information about needed steps for your local development environment after the refactoring and on how to resolve the merge conflicts when rebasing.
Is somebody available for a debug-session? I having problems while working on the requested changes in #444.
I can't running (and writing) stf tests like https://github.com/saros-project/saros/blob/master/eclipse/test/stf/saros/stf/test/session/DerivedResourcesTest.java by simple click on "run Junit-Test" in Eclipse. Which set up is necessary? Is there available any help/manual ?
If the new guide is not sufficient, please add the missing information from the old documentation :wink: .
Hey there 👋So I submitted my first PR to the Saros project and also addressed feedback of the initial review round. (Thanks for providing the feedback that quick!) Now I wondered about the expected commit message style for those commits where I address review remarks. Since the PR is probably squashed upon merging (is this the case?) the commit message tags (INTERNAL, DOCS, etc.) are probably not all that relevant. What's common here? Sticking to the format just for aiding during review, or is this not defined that exact?
Here's the PR as reference: saros-project/saros#482
Hello David, welcome and thanks for your first PR!
Since the transition to github is more or less in progress, the new guidelines page is not yet actively published, but contains information about the tags used for commit messages and the review process description is here.
So the guidelines state that every commit message should be formatted accordingly, but this is a child of the Gerrit Review era when squash was not used. As you suspected, your commits are candidates for squashing and since your messages are meaningful enough for review, it looks good for me.
Since the transition to github is more or less in progress, the new guidelines page is not yet actively published, but contains information about the tags used for commit messages and the review process description is here.
So the guidelines state that every commit message should be formatted accordingly, but this is a child of the Gerrit Review era when squash was not used. As you suspected, your commits are candidates for squashing and since your messages are meaningful enough for review, it looks good for me.
Hey, is somebody available to take a look at #212. For unknown reason the build is queued forever. I need a review, too.