-
1. Re: Is RichFaces 5 BOM Unnecessary?
manarh May 9, 2013 3:52 AM (in response to lfryc)if Richfaces dependencies are really just org.richfaces:richfaces:jar and bunch of optional dependencies it could be a kind of a useless. But the point of optional dependencies is important, because if you know that only these versions are working and newer or older could bring different issues, I would vote for RF BOM ;-).
-
2. Re: Is RichFaces 5 BOM Unnecessary?
bleathem May 9, 2013 8:30 AM (in response to manarh)+1 for bringing this issue up Lukas.
To manage the push dependencies, we could introduce a richfaces-push-depchain. This would transitively bring in the atmosphere dependencies of the correct version.
The cache providers is something we were already talking about spinning out as a separate jar (RF-12953) - these versions could be managed transitively there too.
Brian
-
3. Re: Is RichFaces 5 BOM Unnecessary?
lfryc May 14, 2013 5:03 AM (in response to bleathem)As we have discussed it with a Brian little bit further,
we had following points:
- Push dependencies
- should we stay consistent between maven and non-maven users?
- it is not necessary, each of the build systems have different perspective
- we will allow to bring the Push dependencies using depchain mechanism
- maven users specify richfaces.jar, richfaces-push.jar (or richfaces-push-depchain.pom) dependencies
- tracker here: https://issues.jboss.org/browse/RF-12974
- should we stay consistent between maven and non-maven users?
- Cache providers version management
- we will leave a richfaces-bom around for a while to manage those dependencies
- the JDF's -with-richfaces BOM can manage dependencies
- brings JavaEE BOM
- manage version of richfaces.jar, richfaces-push.jar and cache providers
- brings JavaEE BOM
- Push dependencies