Community
Participate
Working Groups
See attached screenshot. Notice the cancel button is disabled. For some reason, the act of calculating requirements and dependencies was taking way too long (maybe network or server problems; who knows). Anyway, I wasnted to cancel the operation and try again later, but I didn't have the option. I had to open the task manager and hard-kill the process.
Created attachment 167334 [details] screenshot
The red "stop" button next to the progress bar will cancel the calculation.
I think there is a separate problem with downloading these jars in the first place. See bug 311929 and bug 311776
In the screenshot, the [x] contact all sites checkbox is checked, which means that all enabled sites are being loaded at this time. Another change in M7 is that artifact repo references are followed and loaded at resolve time, whereas before they were loaded at collect time. That's what's happening in this picture...the artifacts.jar for one of the enabled sites is being downloaded.
(In reply to comment #2) > The red "stop" button next to the progress bar will cancel the calculation. Indeed. I did not see the red box. User error.
(In reply to comment #5) > (In reply to comment #2) > > The red "stop" button next to the progress bar will cancel the calculation. > > Indeed. I did not see the red box. User error. In your defense, the cancel button used to work, and it was bug 287887 that introduced the red button (because many users never knew that cancel worked in this way). So it was your muscle memory. ;-)
(In reply to comment #6) > In your defense, the cancel button used to work, and it was bug 287887 that > introduced the red button (because many users never knew that cancel worked in > this way). So it was your muscle memory. ;-) Funny. Well, I think 287887 took things too far. In my case, I wanted to cancel out of the whole Update Manager operation, not just the sub-task of getting the requirement and dependencies. For that situation, the intuitive place to go is the Cancel button in the dialog. Having to cancel the sub-task and then cancel out of the dialog seems both unintuitive and onerous. I think it's good that the sub-task can now be canceled, but I think the ability to cancel out of everything (with a single click) is still desirable.
(In reply to comment #7) > Funny. Well, I think 287887 took things too far. In my case, I wanted to cancel > out of the whole Update Manager operation, not just the sub-task of getting the > requirement and dependencies. For that situation, the intuitive place to go is > the Cancel button in the dialog. Having to cancel the sub-task and then cancel > out of the dialog seems both unintuitive and onerous. I think it's good that > the sub-task can now be canceled, but I think the ability to cancel out of > everything (with a single click) is still desirable. Well, you never had the single click cancel, even before bug 287887. You would have to cancel once to stop the operation, and then cancel again to get out of the wizard. What that bug did was separate those two, because redefining the meaning of the cancel button on the fly was tripping people up.
(In reply to comment #8) > (In reply to comment #7) > > Funny. Well, I think 287887 took things too far. In my case, I wanted to cancel > > out of the whole Update Manager operation, not just the sub-task of getting the > > requirement and dependencies. For that situation, the intuitive place to go is > > the Cancel button in the dialog. Having to cancel the sub-task and then cancel > > out of the dialog seems both unintuitive and onerous. I think it's good that > > the sub-task can now be canceled, but I think the ability to cancel out of > > everything (with a single click) is still desirable. > > Well, you never had the single click cancel, even before bug 287887. You would > have to cancel once to stop the operation, and then cancel again to get out of > the wizard. What that bug did was separate those two, because redefining the > meaning of the cancel button on the fly was tripping people up. Fair enough. I've never had to cancel out that dialog, so I wasn't sure what the previous behavior is. From what you describe, it certainly was confusing. So, I guess what I'm basically stating is a feature request. I'll open a new bugzilla for that.
