Running different releases at the same time?

Classic Servoy
1

Hi!

Is it possible to run different releases of the same solution on the same server at the same time?
If I rename the solution while making a build and import it to server it just updates the existing solution and activates the new release.
What I need is to be able to run both releases (e.g. we’re introducing new features/updates and let selected users test them).

Is there a way to rename a solution?

Cheers,
Maria

2

If you select the option “Clean import” when you import a solution, you can provide a new name.

Note though that once imported as a clean import, the solution gets a new internal unique ID. So, if you do the import on an application server, you will not be able to update that “new” solution that was created by the clean import, because the Id of the solution is only known on that application server (and thus not in developer where you’d make updates etc.)

Paul

3

pbakker:
If you select the option “Clean import” when you import a solution, you can provide a new name.

Note though that once imported as a clean import, the solution gets a new internal unique ID. So, if you do the import on an application server, you will not be able to update that “new” solution that was created by the clean import, because the Id of the solution is only known on that application server (and thus not in developer where you’d make updates etc.)

Paul

This is what I tried doing, Paul, but it comes up with this error:

[error]	com.servoy.j2db.persistence.RepositoryException: There is already a solution with the name test_app

Whether I build the solution with the same name or not, if I do a clean import the error is always there :(

The solution references two other modules that are included in the export file. Should this be the reason?

4

A clean import requires a new name.

Are you saying that you do provide a new name, but it still complains that a solution with that name already exists?

The solution name in the error you posted, is that the old or new name of the solution, or is that the name of one of the modules?

Paul

5

Hi,

I have the same problem.
We have a Solution Webshop (with a underlying module Framework)

At importing I used clean import with a new name: Webshop_JJ, but it gives the same errormessage:
‘There is already a solution with the name Webshop_JJ’

Is it a problem that there is an underlying module Framework? Is that module also renamed? Or will the original Webshop solution and the new Webshop_JJ (if i could import it) both reference to the same framework version?