Inccorect BOM definition
See original GitHub issueBOM, aka Bill-of-Material, is a “pom” type artifact that declare all modules with version of current component.
Commonly, BOMs should NOT contain declarations not belong to current component.
However, seata-bom
imports spring-framework-bom
and declares all dependencies seata use except the seata modules.
This is really a bad practice and it breaks the semantic of BOM!
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
Bill of Materials (BOM) Meaning, Purpose, and Types
A bill of materials (BOM) is a centralized source of information containing a list of items used to manufacture a product and the...
Read more >Four sources of errors in Bill of Materials (BOMs) - Medium
BOM management mistakes are very costly can easy cause delays in manufacturing, messy supply chain or products missing their targets. I covered ...
Read more >5 Problems That Can Arise from an Inaccurate BoM
Wrong Component Quantity/Inaccurate Inventory – Inaccurate inventory can lead to stalls in production, adding valuable time to the overall product design cycle.
Read more >What is a bill of materials (BOM)? - TechTarget
A bill of materials lists the components and assemblies required to manufacture a product. Learn how to create an effective BOM and the...
Read more >5 common problems associated with incorrect or incomplete ...
The root cause of the identified problems often centre around Bill of Material (BoM) data within an organisation's CMMS, which is commonly incomplete,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@JasonMing In fact, I think it is more reasonable to replace ‘seata-bom’ with ‘seata-dependencies’.
BTW, for more refined control of build, It’s better to replace maven with gradle, like spring/spring-boot and many opensource projects did. If using gradle, the bom will no longer require enumerating all modules by hand, and root project can configure the common settings for all submodules in one place. That will more friendly for managing the standalone modules like “seata-bom” and “seata-all”.