facebook

Upgrade from 6.0M1 problems

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #274198 Reply

    henk
    Member

    I tried to upgrade my Eclipse 3.3/MyEclipse 6.0M1/Windows XP SP2/Java 6.02 installation for MyEclipse 6.0GA. Using “Find and Install… > Search for updates of currently installed features”, Eclipse did not find the 6.0GA update. Naturally my “Valid Updates” setting had been set to “compatible”.

    However, I was surprised when I looked at “Find and Install… > Search for new features to install > MyEclipse discovery site”, “MyEclipse Enterprise Workbench version 6.0GA” was listed there. When I unfolded this, it listed “MyEclipse Enterprise Workbench 6.0.0.zmyeclipse60020070820” as a child, so that should be the one.

    Nevertheless I wonder, why is the update listed between the new features instead of being seen by the updater?

    #274214

    Matt Bucknam
    Participant

    I’m noticing the same thing.

    #274235

    Riyad Kalla
    Member

    Great questions guys.

    The way the Eclipse Updater works is simply compares versions IDs on plugins. So when we do the milestone builds, in order for them to have a version “smaller” than the final GA release, we use numbering like: 5.9.100 == 6.0 M1, 5.9.200 == 6.0 M2, and so on. So that way 6.0.0 shows up as the final release.

    Unfortunately the Eclipse Updater does not support major-version-changed updates (5.x -> 6.x), that’s considered a “new install”. So once you do that “new install” and restart, all the new 6.0.0 versions of the plugins get picked up and loaded instead of the older 5.9.100 ones… so the end result is basically an update, but because of limitations in the Eclipse Updater, it’s not actually called that.

    #274238

    henk
    Member

    Hi Riyad,

    Thanks for clarifying that 🙂 You might want to update the announce posting. It says to use the regular updater, so I figure more people will be surprised when it doesn’t find anything.

    Wouldn’t it be an option btw to give the final release a non .0.0 number? I.e. name M1 6.0.1, M2 6.0.2, etc up until 6.0.x for the final GA release?

    #274249

    Riyad Kalla
    Member

    Then what do we version 6.0.1? 🙁

    For most folks the Quick Install should show them the update right after they launch… I’ll change the announcement though, you are right it’s a bit confusing.

    #274308

    henk
    Member

    Then what do we version 6.0.1? 🙁

    Well, the simplest answer would be to not do a 6.0.1 and go straight for a 6.1, where 6.1.1 would me M1 and 6.1.x would be the final GA release again. If 6.0.1 is a really minor release, just increment the version number to 6.0.(x + 1). It’s perhaps confusing, I’ll agree to that ;). On the other hand, companies like Microsoft and Apple use build numbers which they expose to regular customers and which also do not correspond to the official version of the product.

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: Upgrade from 6.0M1 problems

You must be logged in to post in the forum log in