Auto-enter changes don't update via SVN

Classic Servoy
1

Servoy 4.1
MySQL 5.0
Windows XP / Mac Leopard
Subversive SVN client

I added an auto-enter parameter to a field in my table. I then did a commit/update in SVN. When another developer does an update of SVN, the auto-enter changes are not pushed back down to him. (I don’t believe new fields are pushed down to him either)

When doing an import/export in Servoy 3.5, these changes were included.

Is there a way to automatically push or pull these types of DBserver changes when working with SVN and multiple developers?

2

Jason,

Database structure changes and auto-enter values are not stored at the solution level but in the resources project.
/datasources//

.dbi

Have you committed these as well?

Rob

3

So I clicked on Resources, Team, then Share Project, to add resources to SVN.
When asked for a location in my SVN repository, I added the Resources project in a subdirectory underneath my solution directory.
It now shows an SVN version number and repository location next to the word Resources in the navigation tree, so looks like everything worked correctly.

My DBservers also show SVN info, so I assume they were included in the Resources commit as well. Yes?

Will a commit of my solution also update Resources and vice versa, or do I need to commit them separately?

Thanks for the tip.

4

I need some SVN guidance on Resources.

I did a SHARE on my resources and they are now showing as in SVN.

When a new developer wants to get my project from SVN and get the RESOURCES too, how do they download the resources? When we tried it, the resources project from SVN shows up now as a normal solution, but not as a resource.

Servoy 4.1 build 651
Windows XP
Subversive plugin
Mysql
ProjectLocker for online SVN

5

Jason,

A solution and a resource project are both projects in eclipse terms with a special tag (called nature), solution nature and resources nature.
Servoy will look at these natures to distinguish these eclipse projects from other non-servoy projects.

Second, a solution has a reference to the resources project it uses.

So if you have a solution called sol and it uses a resources project called res, you have to share them both (preferably to the same svn repository).

Other developers can import these 2 directories from svn and they should appear the same as in your workspace (the nature and project refs are all saved in svn and downloaded by the other developers)

If for some reason the natures are not as expected you can change them using the context menu on project explorer view.

Hope this helps,

Rob