When commiting my solution from Eclipse to update the Repository, I get message
com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: Branching is not supported, only the last release can be updated
But on my server I see 2 releases, with release 2 active.
I did create a new release, earlier today, but Developer has been quited and server has been restarted
So this message is wrong. How can I resolve this problem?
What did you checkout in developer, the head or a specific version ? Issue is if you checkout a specific release, then a new release is created on server you cannot perform team operations from that checkout. If you checked out head it should work ok.
My solution was originally checked out as release 1
I commited by solution
I quited developer
I used button ‘New release’ within my application server (because I wanted to keep the previous release)
I set the new release (release 2) on active
I restarted the application server
I started developer again and I wanted to make my changes for release 2
I think I even first did a Synchronize again in developer
I could make changes, but on commit of my changes I got the error
I haven’t found some setting in the developer to set local release also on release 2
Finally I got Server Developer working again by creating a new workspace and checkout all my solutions.
But that is a lot of work after creating only a new release, so I won’t use this again.
Martin
As I said everything would have worked fine if you checked out Head instead of release 1 (even if there is just one release they are not the same). If you check out a specific release it will only work to commit while it is the latest release on server. So, in your situation, indeed the solution is to checkout again (and make sure you checkout head).
lvostinar:
As I said everything would have worked fine if you checked out Head instead of release 1 (even if there is just one release they are not the same). If you check out a specific release it will only work to commit while it is the latest release on server. So, in your situation, indeed the solution is to checkout again (and make sure you checkout head).
I always checkout HEAD. When I checked out originally, it was the HEAD that I checked out (there wasn’t a release 2 at that moment)
This means that if you change the release on the server, that you always have to re-checkout again.
Why isn’t there a simple option ‘Update release’ so that you can easy set your local version to the same release.
I just tried this scenario with a small sample but it works ok for me (checkout head, create new release, modify in developer, commit ).
Why isn’t there a simple option ‘Update release’ so that you can easy set your local version to the same release.
Good question, you can open a case about this.
OK, I will
By the way, the error occured (only) on valuelist (created after the the release upgrade)
martinh:
OK, I willBy the way, the error occured (only) on valuelist (created after the the release upgrade)
I created a new form and committed it without problems.