Hi Sanneke,
it occurred to me yesterday when I was trying to get another person to help me to develop a solution using the framework (FW), that if you keep on releasing each change/update/fix as a solution for importing, my SVN setup with my other developer is not going to work, as it will lose the references to items that I link my local FW copy (or, I think, not allow me to import a local version).
I ‘shared’ it on my SVN with them and that is fine for the current version as it is, but if you create a new release that I have to import locally from a ‘.servoy’ file, everything is going to break.
Would it be possible to put the FW onto an SVN there and give every company/developer group that has the FW a username & password to be able to ‘checkout’ the FW, then anytime you issue a new release, we can just sync with the SVN to get the changes.
Then, in a multi-developer situation, each developer within a company/developer group can then be linked to the same SVN for the FW and there shouldn’t be any issues.
Am I missing anything (I am not an expert in SVN, but have made an assumption about what is going to happen…)???
Thanks
Rafi