Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2477

consolidate maven settings configuration into own module

    XMLWordPrintable

Description

    We've got a couple different, identical, jboss-settings.xml files:

    cct_module/jboss-maven/added/jboss-settings.xml
    cct_module/os-java-s2i/added/s2i/jboss-settings.xml

    That get configured by a couple different ways.

    The first way is for s2i builds. And if you include the s2i modules, this is common.sh script is available to you during assembly:
    cct_module/blob/master/s2i-common/common.sh
    cct_module/blob/master/os-jws-s2i/added/s2i/assemble
    cct_module/blob/master/os-java-s2i/added/s2i/assemble
    cct_module/blob/master/os-eap-s2i/added/s2i/assemble
    jboss-kie-modules/os.kieserver.s2i/added/s2i/assemble

    The other way is for business central, decision central, and kieserver (in realtime decision server, intelligent process server, and bpmsuite business central and kieserver):

    cct_module/os-eap-launch/added/launch/maven-repos.sh

    The functionality of these two scripts, and anything else maven settings configuration-wise, should be combined into a single cct_module.

    The reason not everything can move into the os-java-s2i module is that not all images (like business central or decision central) use s2i, and thus don't include that module.

    And the maven-repos.sh script isn't really specific to eap, so shouldn't live in the os-eap-launch module.

    As long as all places that need this functionality (either in s2i phase or launch phase) specify this module, then they will have access to the combined functionality.

    Attachments

      Issue Links

        blocks

        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) CLOUD-2293 Release OpenJDK community images

        • 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) CLOUD-2867 Create an OpenJDK 8/RHEL 8/X86_64 image

        • 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) CLOUD-2868 Create an OpenJDK 11/RHEL 8/x86_64 container image

        • 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) CLOUD-2869 Create an OpenJDK 11/ RHEL 7/ X86_64 container image.

        • 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
        is related to

        Task - Represents a small unit of work that is not end-user facing. RHPAM-1536 kieserver environment needs updating upon upgrade to CE sprint-24

        • 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
        relates to

        Feature Request - Feature requests from customers and/or users CLOUD-2465 Allow custom location for local maven repository

        • 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) CLOUD-2997 [tracker] [JWS31] Sprint 25 release

        • 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

            rcernich1 Rob Cernich
            dward-se-jboss David Ward
            Marek Schmidt Marek Schmidt
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: