[jboss-jira] [JBoss JIRA] (DROOLS-1137) Better granularity for imported BOMs

Petr Široký (JIRA) issues at jboss.org
Fri Apr 22 09:01:00 EDT 2016


    [ https://issues.jboss.org/browse/DROOLS-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195740#comment-13195740 ] 

Petr Široký edited comment on DROOLS-1137 at 4/22/16 9:00 AM:
--------------------------------------------------------------

Yes, ultimately {{kie-parent-with-dependencies}} should go. I will keep it around until all the repos are migrated (I would like to do the migration one repo at a time). About `kie-platform-bom`, I am not sure what the value is. Our projects won't use it, but it might be useful for our users in case they want single POM which will import all the versions they need. This initial proposal does not include it, but we may decide to add it back later on.


was (Author: psiroky):
Yes, ultimately `kie-parent-with-dependencies` should go. I will keep it around until all the repos are migrated (I would like to do the migration one repo at a time). About `kie-platform-bom`, I am not sure what the value is. Our projects won't use it, but it might be useful for our users in case they want single POM which will import all the versions they need. This initial proposal does not include it, but we may decide to add it back later on.

> Better granularity for imported BOMs
> ------------------------------------
>
>                 Key: DROOLS-1137
>                 URL: https://issues.jboss.org/browse/DROOLS-1137
>             Project: Drools
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 6.4.0.Final
>            Reporter: Petr Široký
>            Assignee: Petr Široký
>
> Projects/modules like Drools or OptaPlanner transitively require BOMs which are not actually needed at all (e.g. uberfire-bom or guvnor-bom). This brings a lot of issues for RPMs and is also weird.
> Proposal to fix this (discussed with [~ge0ffrey] as the best option):
> *kie-parent (created from kie-parent-metadata)*
>  * has ip-parent as it’s parent
>  * Does not contain dependency versions (empty dependencyManagement)
> *user-boms (kie-bom, drools-bom, optaplanner-bom, etc)*
>  * have kie-parent as their parent
>  * contain only depMgmt for the specific groupIds (e.g. org.optaplanner for optaplanner-bom)
>  * nothing really changes here
> *kie-third-party-bom*
>  * imports ip-bom to get the depMgmt
>  * contains required overrides
>  * does _not_ declare any versions for KIE deps (not even UF or Dashbuilder)
> Specific projects then import only what they need (obviously not 100 % true as the kie-third-party-bom would define many more versions than we need, but that is not easily fixable atm):
> *Drools parent POM (top-level pom in drools repo)*
>  * has kie-parent as it’s parent
>  * imports kie-third-party-bom + drools-bom
> *jBPM Console NG parent POM*
>  * has kie-parent as it’s parent
>  * imports kie-third-party-bom + drools-bom? + jbpm-bom + uf-bom + uf-ext-bom + dashuilder-bom + guvnor-bom



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the jboss-jira mailing list