Confluence 5.1.3 installer: Very smelly! Atlassian, please improve it!

[samjones6]

upgrading 4.1 to 5.1.... should be easy, right?

Not. (at least: Not on Win2003 server with latest java JRE)

installer error #1: Cannot delete the confluence directory.... (well yes, that is because tomcat is still running and has a bunch of files locked in there... the "apache tomcat" service was created by a confluence installer, so it should be detected by the installer..)

installer error #2: "undefined variable exception" OK, whatever.

installer error #3: I didn't catch. something about install4j blowing up in some way

post install issue #1: my mods to server.xml were wiped out. So gotta figure it all out again (to get ssl back in gear). // Every update I have done to confluence over the years has this issue. I have to re-discover ssl every year or two.

If it was more reliable to upgrade confluence.... we would do it more often.... The Fog Creek guys are many miles ahead of atlassian here.

Atlassian: Can you make the install process smoother?

[Ellen Feaheny [AppFusions]]

The upgrade process has improved miles over the past 1/2 dozen Confluence releases, every time.

But surely trickier when skipping releases, which candidly is always a challenge in high-feature server operations, understandably.

Don't know if these help any - since at least 4 notes sets to consider. But take a look.

https://confluence.atlassian.com/display/DOC/Upgrade+Notes+Overview

As well as the release notes:

https://confluence.atlassian.com/display/DOC/Confluence+Release+Summary

And Java JRE/JDK update to 1.7 with Confluence 5.

https://confluence.atlassian.com/display/DOC/Supported+Platforms

Hope that helps.

[samjones6]

I will agree that the upgrade process has improved.

However it is still really bad.

I simply expect a professional, robust, installer/upgrader, and 5.1.3 isn't it.