atlas-run-standalone always starts latest confluence version

[Florian Zöllner [Communardo]]

Hi,

I'm always using atlas-run-standalone to start local Confluence systems to test confluence features, even with older Confluence versions (like 3.5.x or 4.3.7). Since yesterday it it always starts the lastest 5.1.3 Confluence version regardless of what I actually started e.g. with "atlas-run-standalone --product confluence -v 4.3.7".

Does anyone know what I might do wrong and how I can get a local older version of CF?

Cheers

Florian Zoellner

[Boris Georgiev _Appfire_ · Accepted solution]

Possible problem might be that you've previously run anbother version of confluence in the same folder. According to the docs you have to always clean the folder before switching to another version of a product run with "atlas-run-standalone" command.

Please provide the output of the atlas-run-standalone command (or at least the first 30 lines) so more details are available like:

• Your SDK version / amps plugin version
• The actual call to mvn generated by atlas-run-standalone

I've tried to run the version you mentioned on my machine with the latest SDK and it runs fine.

[Florian Zöllner [Communardo]]

Thank Boris for your answer.

In the meantime I found that I can't start < CF 4.0 with the new SDKs. (source. answers thread)

Correctly working with different folders might have also been an issue for me. ;-)