Provide a joinfaces bom without spring-boot-dependencies

[cachescrubber]

Provide a joinfaces bom without spring-boot-dependencies

[larsgrefer]

The biggest problem with this is to find suitable names for the - then two - JoinFaces BOMs 😅

Technically we could have a BOM A which includes the joinfaces modules and dependencies like Primefaces and then a second BOM B which includes BOM A and spring-boot-dependencies.

For backward compatibility, it would make sense to name BOM B joinfaces-dependencies as it would behave like the current implementation, but what would be good name for the new BOM A?

[cachescrubber]

Software developer thinking of a good name for a variable. 😄

For backward compatibility: How about joinfaces-only-dependencies?

[larsgrefer]

That tweet sums it up :D

Spring Framework has two artifacts:

framework-bom (only includes the spring artifacts itself)
framework-platform (includes dependencies and boms of other projects)

[jomu78]

What about "joinfaces-project-dependencies" for BOM A?

[persapiens]

If we follow Spring Framework conventions, people may find JoinFaces artifacts easier.

[larsgrefer]

I've decided against backward compatibility and for (hopefully) better names:

The "old" joinfaces-dependencies is now joinfaces-platform
The "new" joinfaces-dependencies is now only contains external dependencies
joinfaces-bom only contains org.joinfaces artifacts.

I've also added a little diagram to the documentation to show the relationship between the different artifacts:
https://docs.joinfaces.org/5.2.x-SNAPSHOT/reference/#bom

[cachescrubber]

Good Choice - If it wasn't for backward compatibility I would have come up with the same structure.Thanks for your effort.

[cachescrubber]

Thanks @larsgrefer - I just updated an app to 5.2.0 using the new bom imports. Importing joinfaces-bom + joinfaces-dependencies at the leaf of a dependency tree no longer overrides the spring-boot version and dependencies.