[kepler-dev] [Bug 5494] New: existence of remote 2.2 patches can cause 2.3 to fail to start 2.2 on first attempt

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5494

           Summary: existence of remote 2.2 patches can cause 2.3 to fail
                    to start 2.2 on first attempt
           Product: Kepler
           Version: trunk
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: module manager
        AssignedTo: welker4kepler at gmail.com
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


Now two patches to 2.2 exist: loader-2.1.1 and module-manager-gui-2.2.1.
If you launch 2.3.0 from the 2.3 app and attempt to use it to switch back to
kepler-2.2, if you have not previously downloaded the patches mentioned above
from within 2.2, 2.2 will fail to start on this initial attempt. The error on
console is:
9/19/11 4:34:20 PM    [0x0-0xfdafda].org.kepler.build.runner.Kepler[38570]     
   [null] Error: The following modules are missing: 
9/19/11 4:34:20 PM    [0x0-0xfdafda].org.kepler.build.runner.Kepler[38570]     
   [null]   loader-2.1.1
9/19/11 4:34:20 PM    [0x0-0xfdafda].org.kepler.build.runner.Kepler[38570]     
   [null]   module-manager-gui-2.2.1

A subsequent start up of the 2.3 app does what was supposed to happen the first
time: start 2.2, immediately prompting you to download the two available
patches.

During the Module Manager restart process something seems to have knowledge of
remote patches and mistakenly assumes they've been downloaded.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.