Is RTC Eclipse client supposed to notice changes made at JazzHub?
related to https://jazz.net/forum/questions/142486/why-is-jazzhub-demanding-to-launch-a-new-app-when-i-have-one-that-just-needs-to-be-updated
After making the app.js source change at jazzhub I refreshed Pending changes in my RTC client (thinking I'd pull the change in) and it shows no pending changes. So now my source on my local system and my source at JazzHub are out of sync. So it would seem a checkin from JazzHub was necessary...
Unfortunately, I tested the other direction first -- made another change in the Eclipse client and delivered it. Then when I tried to checkin at JazzHub, I got an error that suggested I do something (create a patch) that doesn't seem to be possible from the JazzHub UI.
Trying to resolve it, I attempted to discard change sets from the jazzhub UI in hopes of getting back to the beginning -- but it refused with the same error/suggestion shown above. I did eventually find a way to reload the jazzhub version (which lost those changes).
After playing with this some more, it seems that I have a single, shared workspace at jazzhub that is being used both by my JazzHub Orion editor and my local RTC. When I checkin a change at JazzHub, the RTC client will show as out-of-sync when I refresh Pending Changes. When I reload, it has the change from JazzHub -- and it is shown as outgoing towards the stream.
Is there a way to notice that someone has connected to the same workspace from two different clients simultaneously? While most of my pain here turns out to be my own fault, I doubt I'll be the last person to run into this.
Accepted answer
Millard,
it is important that you create a new workspace. JazzHub Creates one internally for displaying the source. From Eclipse, you have to create your own.
I ran into the same trap and since then use a Naming Patten e.g. JazzHubWorkspace.
There is no way to tell you run on the same workspace in two different contexts. Even if you use Eclipse alone, you can run into that mistake. Just avoid this problem.
it is important that you create a new workspace. JazzHub Creates one internally for displaying the source. From Eclipse, you have to create your own.
I ran into the same trap and since then use a Naming Patten e.g. JazzHubWorkspace.
There is no way to tell you run on the same workspace in two different contexts. Even if you use Eclipse alone, you can run into that mistake. Just avoid this problem.
Comments
The easiest solution is to use two different repository workspaces. Another option is to reload the repository workspace whenever you switch between the clients.
We are working on a way to make this more clear and a better experience.
Thanks, @rschoon. Yeah, once I realized what had happened it was clear that I shouldn't be doing that. But it was very easy to step into this trap and I'm glad to hear we're going to try to make it harder.