Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-15476

Allow users to provide downloadable cartidges

    XMLWordPrintable

Details

    Description

      OpenShift allows lately to provide your very own cartridge by giving it a git-url where the cartridge source may get cloned from. In the Web-UI this looks as follows:

      Attachments

        1. 2013-09-30 17.14.bmml
          44 kB
        2. 2013-09-30 17.14.bmml
          55 kB
        3. 2013-09-30 17.14.bmml
          41 kB
        4. 2013-09-30 17.14.bmml
          38 kB
        5. 2013-09-30 17.14.bmml
          38 kB
        6. 2013-09-30 17.14.bmml
          29 kB
        7. 2013-09-30 17.14.bmml
          39 kB
        8. 2013-09-30 17.14.bmml
          39 kB
        9. 2013-09-30 17.14.bmml
          39 kB
        10. 2013-09-30 17.14.bmml
          27 kB
        11. 2013-09-30 17.14.bmml
          27 kB
        12. 2013-09-30 17.14.bmml
          26 kB
        13. 2013-09-30 17.14.bmml
          26 kB
        14. 2013-09-30 17.14.bmml
          33 kB
        15. 2013-09-30 17.14.png
          2013-09-30 17.14.png
          485 kB
        16. add-cartridge.png
          add-cartridge.png
          116 kB
        17. add-downloadable-cartridge.png
          add-downloadable-cartridge.png
          17 kB
        18. create-new-or-import-existing.png
          create-new-or-import-existing.png
          71 kB
        19. crobson_2014-01-28 16.11.png
          crobson_2014-01-28 16.11.png
          78 kB
        20. downloadable-cart-embedded.png
          downloadable-cart-embedded.png
          75 kB
        21. downloadable-cart-type.png
          downloadable-cart-type.png
          83 kB
        22. embedded-cartridges-listing.png
          embedded-cartridges-listing.png
          45 kB
        23. new-application-1.png
          new-application-1.png
          104 kB
        24. new-application-2.png
          new-application-2.png
          70 kB
        25. select-existing-application.png
          select-existing-application.png
          56 kB

        Issue Links

          blocks

          Sub-task - The sub-task of the issue JBDS-2775 Support downloadable cartridges in OpenShift UI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users JBDS-2865 Support downloadable cartridges in OpenShift UI

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Feature Request - Feature requests from customers and/or users JBIDE-14744 Allow users to choose from quickstarts/templates when creatingApplication wizard: new application

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-16903 Application wizard: application type label should show full cartridge name (predefined carts: short-name, downloadable carts: url)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-16904 Application wizard, Embed wizard: Code Anything: url text field should offer what I already used (content-assist)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          duplicates

          Feature Request - Feature requests from customers and/or users JBIDE-14394 support adding cartridge via github url

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-15655 Application Wizard: errors "you have to choose an application name" even though I have chose an existing app

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-13233 Application wizard: Button 'Select All' in Setup OpenShift Application dialog does nothing

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-16374 Application wizard: should be able to see all domains/apps when choosing an existing application

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-11811 Embed wizard: Should have "Embed None"

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users OSJC-9 openshift-java-client: add support for downloadable cartridges

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-16830 New application wizard: I dont get warned if I have mysql & phpmyadmin embedded, then remove mysql

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-12457 Application wizard: changed settings are not used when I let the clone fail (by refusing to store the new host fingerprint)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-16509 Application wizard: Embedded cartridges should get verified when I select "Enable Scaling" AFTER I selected them

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-16598 Application wizard: domains combo is not refreshed if I rename a domain via "Manage Domains"

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-15654 Application wizard: merge existing / new application forms into a single one

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              adietish@redhat.com André Dietisheim
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: