Hide Forgot
Description of problem: See attached screenshot - these quickstarts are actually installed successfully: tree -L 1 * dtgov ├── dtgov-demos-project ├── dtgov-demos-switchyard └── pom.xml sramp ├── pom.xml ├── README.md ├── s-ramp-demos-archive-package ├── s-ramp-demos-classifications ├── s-ramp-demos-custom-deriver ├── s-ramp-demos-derived-artifacts ├── s-ramp-demos-mvn-integration ├── s-ramp-demos-ontologies ├── s-ramp-demos-properties ├── s-ramp-demos-query ├── s-ramp-demos-relationships ├── s-ramp-demos-shell-command ├── s-ramp-demos-simple-client ├── s-ramp-demos-switchyard └── s-ramp-demos-switchyard-multiapp Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 833700 [details] Screenshot
The reason for this is because the quickstarts pack as displayed in the installer is a "flag" pack for the true, underlying packs. Thus, IzPack reports the pack as size 0B because it doesn't contain any files; instead, it indicates that the hidden packs that actually contain the quickstarts to be installed or not. This is actually as intended, because it means that only relevant quickstarts will be installed. For example, if the user deselects S-RAMP and DTGov, their quickstarts will not be installed, instead of the user having to deselect independent "S-RAMP Quickstarts" packs. If the Quickstarts pack is deselected, no quickstarts will be installed at all. These changes are due to our UX discussions. It's kind of confusing, so here are some use cases about what will happen. My suggested solution is just to remove the 0B label and have it be just blank. Alternatively, we could attempt to calculate the size, but it may be hard to get IzPack to do this without some more involved changes to the TreePacksPanel. Thanks, Tom
Hello, the same issue applies for FSW installer as well. I would suggest add the maximal number that the quickstarts can take. This is definitely better than "we don't know". Another option could be adding quickstarts separately under each corresponding component. But 0B is a complete non-sense and a UX problem. @M.
This was incidentally resolved during a related fix to IZPack's TreePacksPanel. The quickstarts should now display the approximate size of all quickstart packs combined. See: http://git.app.eng.bos.redhat.com/izpack.git/commit/?id=c371df16b3aa1fb45fa53f1cb6f3f71ae8e526e6 http://git.app.eng.bos.redhat.com/izpack.git/commit/?id=1553a8ae6604e1075424d28548d5f6f37cc4e0a3 http://git.app.eng.bos.redhat.com/izpack.git/commit/?id=000a0576b0b2e8c70f4bb5ff286cff1f21d62aa9 This fix also applies to console installation: http://git.app.eng.bos.redhat.com/izpack.git/commit/?id=a2091477225812fe3de3ac4ae1d6618dd7072068
Verified in CR1.