gistfile1.txt

Repo's:

  appformer (= uberfire, dashbuilder, guvnor, ...)
  drools
  kie-wb-common depends on appformer, drools

Old state:
    org uberfire
        repo uberfire
    org kie
        repo drools
            module kie-ci
                needs maven-infra-builder code (20-30 classes)
        repo guvnor
            module guvnor
                needs maven-infra-builder code

Problem:
    repo appformer
        module guvnor
            needs maven-infra-builder code
    repo drools
        module kie-ci
            needs maven-infra-builder code


Proposal A)
    org+repo for maven-infra-builder
        - own version numbering/ release lifecycle (= pain)

Proposal B)
    maven-infra-builder in appformer org
        - drools engine repo depends on appformer org
            - just a feeling problem?

    Sub-proposal B1)
        - plug in of kie specific code into maven-infra-builder

Proposal C)
    maven-infra-builder in kiegroup org
        - cannot release in 1 command (think repository-list.txt) => No go

Proposal D)
    Duplicate maven-infa-builder code
        - bugs bugs bugs

Proposal E)
    appformer goes into kiegroup
        - politically not desired: it's its own project
        - might kill dashbuilder reuse by teiid etc
        + centralization of code

Proposal F)
    Fix maven-resolver (AKA Aether)
    so we don't need that extra maven-infra-builder

    Upgrade maven-resolve and see how much maven-infra-builder code still remain?