Community
Participate
Working Groups
Now, ServerLogger comes to have non-static methods to support a single-process server model. I've chosen EnvironmentMiner class as a place where the ServerLogger instance is created, since I thought that the EnvironmentMiner was always activated. But the EnvironmentMiner is not activated when the USS facility is not constructed in a client and the client tries to connect to the server. So, it seems that the org.eclipse.dstore.core project is the best place to make ServerLogger instance. But, ServerLogger class belongs to org.eclipse.rse.dstore.universal.miners of org.eclipse.rse.services.dstore project. This project has dependence on org.eclipse.dstore.core project. Due to cyclic dependency, the class that belongs to org.eclipse.dstore.core project cannot invoke ServerLogger APIs. To solve the above problem, I think that the ServerLogger class should be moved from org.eclipse.rse.services.dstore project to org.eclipse.dstore.core project. Are there any solutions for this problem ?
Suggestion sounds good to me. I changed the summary, previous value was: Place where the ServerLogger instance is to be made Note that repackaging is a breaking API change so this needs to be done NOW.
I've moved ServerLogger to the org.eclipse.dstore.core.server package of the dstore.core plugin.