![]() ![]() You can easily see what’s up-to-date, what’s staged or not, and compare changes easily. Accessing your existing repositories from SourceTree is as easy as opening up Windows Explorer and dragging all folders in your Git Repositories folder into the navigation pane. It comes with an embedded Git and the install process is easy. Now for Git I’ve started using Source Tree, a free GUI tool for managing Git flows. Views in Eclipse may need refreshing, but you can easily pull your repository into Eclipse’s Git views. But my preference up to now has been to manage source control synchronisation using standard Eclipse. The plugins give the relevant functionality into Domino Designer to manage everything. You can then choose which source control plugin to share the project via, to create the relevant repository. For Git, it’s just a case of downloading the EGit for IBM Domino Designer from OpenNTF (thanks Nathan). Declan Lynch has nicely blogged the steps for installing the Mercurial plugin. The slight difficulty here is that Domino Designer is built on an old version of Eclipse, which limits the plugin versions and functionality available. This is where the relevant source control plugin to Domino Designer comes in. ![]() The on disk project is turned into a source control repository by right-clicking on it and choosing Team > Share Project…. Your on disk project can be accessed from the Package Explorer. ![]() All you have to do is get into the habit of manually syncing, by using Team Development > Sync with On Disk Project…. But if you’re working with server-based NSFs, we don’t need it, so disable it. It will have minimal impact if you’re working on local NSFs only. If those preferences are checked, then it’s like after making any change to each design element, replicating to your local replica and waiting until the replication has completed before doing anything. The best way to think of this is that the on disk project is effectively a local replica of the database. This is done in Domino Designer Preferences, under Domino Designer > Source Control, with two checkboxes for import and export. Linking to specific source control software will move it later to wherever required.Īlso, I’d recommend disabling automatic import / export to the on disk project. It deletes all content in that folder before exporting the NSF. Never, ever, ever create this to an existing folder. ![]() It is created by right-clicking on the NSF in the Applications Navigator in the XPages Perspective and selecting Team Development > Set Up Source Control for this Application…. This is basically a local backup of the database, not associated to any particular source control tool. This is where you (typically) do all your development. That’s mainly because when I tried an existing database, I had to push it up in multiple chunks with Mercurial, but Git took the whole thing in one go.įor those not used to source control, there are three pieces in the puzzle: Your NSF There are a number of source control options, but the ones I’ve used are Mercurial and Git. The way I’ve used it has changed over time and is still changing. For some time I’ve been using source control, predominantly for personal projects. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |