Question

We have been using Domino on a large project for years without any real source-control (other-than server backups). So, I was rather pleased when I noted the latest Designer 8.5.3 has potential integration with SVN.

I was unable get SVN working just by following the original instructions for as already noted on Stackoverflow the update sites have moved. The solution posted on OpenNTF, only half worked, with Domino still croaking at GEF, Mylyn and some other missing plugins. After finding and installing them, I still do not seem to have source-control integration.

What I have now is the ability to create on-disk projects but I do not seem to have any source-control features. I was expecting to see menu items for commit, update, revert …etc – is this how it works in Domino?

I can of course create a repository to commit the on-disk project to but I was hoping for integration inside of Domino. Whilst having years of experience in programming I’m a novice with Eclipse. I assume that I’ve done something wrong with installing the plugins? it was certainly a complicated process trying track down missing plugins.

Has anyone tried this recently and succeeded? What files do I need to install, setting tweak, …etc, to ensure this works? I’m happy to install my Designer fresh and follow a list of instructions.

Also, am I understanding how the integration works? Will I get command integration within Designer or do I have to work separately with the on-disk projects? I was really hoping for this be easy to integrate into normal workflow so I can convert the team to using it (adding too many extra or complicated steps is unlikely to create a conversion).

I posted a screenshot of my installed plugins in case this is helpful.

Mercurial? As an aside, has anyone used Mercurial instead of SVN with Designer? I would rather use Hg as I’m using this for related Dojo projects and will be easier for the team to use one system. However, I will settle for SVN as any source-control is better than non.

Answer 1

Update: This is answer is now out-of-date. It is useful in that it should point users in the right direction but it isn’t really a working answer anymore. I no-longer develop on Lotus Notes so I cannot update it to a current solution.

I managed to figure this out eventually but will post the solution, just in case anyone else has the same trouble.

The answer by Per Henrik Lausten was very helpful as it showed me the route to follow through the menus. The main problem is that I’m not used to how Eclipse works so I didn’t realise you had to go to the “Team” menu and “Share Project” after creating the on-disk project. When I did this I discovered that both SVN and CVS were already available.

I found that SVN did not like the file:// protocol (perhaps a windows issue?) Since, I could not arrange for an SVN server on our network, I decided to go down the Mercurial route. This was better for us as our other projects are stored in Mercurial.

Setting-up Mercurial with Lotus Designer 8.5.3:

1. In Domino preference (File -> Preferences), set: Enable Eclipse Plugins in the Domino Designer section to ticked.
2. Also in the preferences set: Use Binary DXL for source control operations to unticked (File -> Preferences, Domino Designer -> Source Control). Without this ticked I was not getting text for my Lotusscript agents and it would be difficult to compare changes.
3. Go to File -> Application -> Install:
   • Select Search for new features to install and click Next.
   • Click Add Remote Location button
   • Add the url: http://mercurialeclipse.eclipselabs.org.codespot.com/hg.wiki/update_site/stable/ and give it a suitable name
   • Once you’ve added this, ensure it is ticked in the location list and click Finish
   • Design will then search for updates and give you a list. Untick “Only show latest version of a feature per update site”
   • Tick MercurialEclipse 1.6 from MercurialEclipse Stable Releaes. I found that the latest version does not work, however a previous Stackoverflow conversation indicates that version 1.6 does work.
   • Click finish and allow it to install.
   • You will be asked to approve various plugins and then to restart.
   • MercurialEclipse, should now be installed!

4. To start using Mercurial with a Domino Application:
   • Right-click the application in the Applications tab, select: Team Development -> Set Up Source Control for this Application.
   • Give the project a name and choose a location for the project to be stored.
   • Designer will then do a DXL export of the database to your chosen location. A Navigator tab will appear next to Applications.
   • Right-click your new disk-project in the Navigator and select: Team -> Share Project…
   • Select Mercurial from the Repository types and allow Designer to create the repository.
   • You should now have access to various Mercurial functions via the Team menu. (You need to make your first commit.
5. When you make changes you want to commit to source-control, you need to:
   • Right-click the application and choose: Team Development -> Sync with on disk project…
   • Go to the Navigator tab and right-click your on-disk project, selecting team.

Most of the above steps should be obvious but decided to post full details in case anyone struggled like I did with Eclipse and how to use it properly. Once I figured it out, it really was quite easy.