• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • jboss-fuse-6.1
    • jboss-fuse-6.1
    • None
    • None
    • % %

      Working from the 372 build, I did the following:

      1. apply activemq.zip to create version 1.1
      2. Migrated to 1.1.
      2. apply camel.zip to create 1.2 (un-knowingly created it on the root container)
      3. tried to migrate from 1.1 to 1.2. The console said the migration was in progress and may take a moment. Of course it never worked but I had no indication of my mistake.

      Is there anyway to make this a bit more user friendly, i.e. a message appear that you can't migrate directly to a different patch without rolling back first? Or should it actually let you do this?

              g_nodet Guillaume Nodet (Inactive)
              rhn-support-sjavurek Susan Javurek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: