I am using keyword expansion with Visual Studio and JBuilder projects. With Visual Studio, the file automatically reloads after check-in and displays the new revision number. This is not working in JBuilder - the file does not automatically reload - and even worse, it looks like JBuilder has some sort of cache which requires me to close down the application and re-open to see the changed file.
Now, you might assume that this is just a problem with JBuilder (and I wouldn't be surprised). But it works just fine with VSS - JBuilder immediately reloads the file with new revision number after check-in. So it looks like the Vault client is doing things a little differently than VSS, and JBuilder isn't playing nice.
I saw another post on this forum that described the same issue with another editor (I think it was EditPlus) - where it worked in VSS but not with Vault.
Thanks
Keyword expansion not causing file reload in IDE
Moderator: SourceGear
Version info
forgot to mention -
I'm running version 3.1.1 of the Vault client and server.
I'm running version 3.1.1 of the Vault client and server.
Since we haven't tested Vault with JBuilder (it's not one of the IDE's we support), we're not sure why it doesn't reload. Keyword expansion doesn't take effect until the file is checked in. Is there any way to do a checkin and then a fresh get in JBuilder? Can you do the get with the GUI Client if not with JBuilder?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
I am using the GUI client (Vault). It's not integrated with the JBuilder IDE.
Let me repeat the steps, both with VSS and Vault -
VSS (successful):
- Use VSS client to check out a file
- Switch to JBuilder and modify the file
- Use VSS client to check in the file
- In JBuilder, the IDE warns that the file was modified, and if you click 'Yes', it reloads with the new Revision value (expanded keyword)
Vault (unsuccessful):
- Use Vault client to check out a file
- Switch to JBuilder and modify the file
- Use Vault client to check in the file
- In JBuilder, nothing happens. The new Revision number does not appear. I actually have to close the project and re-open to get the updated file (just closing and re-opening the file in JBuilder doesn't work).
The Vault Client does successfully retrieve the new expanded keyword values - I verified this by opening the file in Notepad after a check-in. But somehow, JBuilder does not know that Vault modified the file. But this works when using VSS - apparently Vault is not doing something when it updates the file - or does it differently than VSS.
Thanks[/list]
Let me repeat the steps, both with VSS and Vault -
VSS (successful):
- Use VSS client to check out a file
- Switch to JBuilder and modify the file
- Use VSS client to check in the file
- In JBuilder, the IDE warns that the file was modified, and if you click 'Yes', it reloads with the new Revision value (expanded keyword)
Vault (unsuccessful):
- Use Vault client to check out a file
- Switch to JBuilder and modify the file
- Use Vault client to check in the file
- In JBuilder, nothing happens. The new Revision number does not appear. I actually have to close the project and re-open to get the updated file (just closing and re-opening the file in JBuilder doesn't work).
The Vault Client does successfully retrieve the new expanded keyword values - I verified this by opening the file in Notepad after a check-in. But somehow, JBuilder does not know that Vault modified the file. But this works when using VSS - apparently Vault is not doing something when it updates the file - or does it differently than VSS.
Thanks[/list]