[
https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761042#comment-12761042
]
Brian Leathem commented on RF-12809:
------------------------------------
Why would we do this? Why not just consume the RichFaces BOM directly? using
[jboss-javaee-6.0-with-richfaces|https://github.com/jboss-jdf/jboss-bom/blob/master/jboss-javaee-6.0-with-richfaces/pom.xml],
which imports the richfaces bom and jboss-javaee-6.0 simply adds more confusin
IMO.
On top of that, we have yet one more place to manage the version increment,
which
[jboss-bom-parent|https://github.com/jboss-jdf/jboss-bom/blob/master/pom.xml#L63]
currently pins at 4.2.0.Final - a very old release.
I prefer leaving the RichFaces BOM in the examples directly, as it is most
clear to those trying to understand the examples.
> Richfaces-related examples should use -with-richfaces BOM
> ---------------------------------------------------------
>
> Key: RF-12809
> URL: https://issues.jboss.org/browse/RF-12809
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Tomas Repel
> Fix For: 4.3.2, 5.0.0.M2
>
>
> There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used
> instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as
> well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation.
> In case of helloworld-rf it is sufficient the dependencyManagement section to
> contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed
> completely.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
richfaces-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/richfaces-issues
